From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v1] doc: update mlx4 flow limitations Date: Fri, 09 Feb 2018 17:39:50 +0100 Message-ID: <1944833.dayHpbUbTZ@xps> References: <1518072954-19082-1-git-send-email-ophirmu@mellanox.com> <20180209162124.GD4256@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Ophir Munk , dev@dpdk.org, Moti Haimovsky , Olga Shern , Matan Azrad , ferruh.yigit@intel.com To: Adrien Mazarguil Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id CCAC71B806 for ; Fri, 9 Feb 2018 17:39:58 +0100 (CET) In-Reply-To: <20180209162124.GD4256@6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 09/02/2018 17:21, Adrien Mazarguil: > This section is titled "Limitations" but contains a mix of features, > limitations and quirks, more like "Random thoughts regarding rte_flow > support". I think this is not what users might expect from such a > documentation which must be exhaustive and consistent. Getting there may > involve tables. +Cc Ferruh > My suggestion is to first get everyone agree on a common rte_flow > capabilities documentation format all PMDs could reuse and then fill in the > blanks. What's your opinion? I think it's better to have some random thoughts than nothing. All the comments you gave in this thread deserve to be written in the documentation as soon as possible. Working on a better standardized documentation (longer term) should not prevent us to write some messy notes in the meantime. Is there already some similar rte_flow notes in other PMD docs? About the common documentation, do you think about a generated table like it is done for other features? Do you plan to provide a template or an example?