From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v7 6/9] ethdev: add common devargs parser Date: Wed, 25 Apr 2018 12:06:13 +0200 Message-ID: <3613685.kkaEeRXftQ@xps> References: <20180328135433.20203-1-declan.doherty@intel.com> <1794949.DGStqB9iLD@xps> <76bc7493-f8cf-0d74-961c-800665744ebe@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Declan Doherty , dev@dpdk.org, Adrien Mazarguil , Ferruh Yigit , Shahaf Shuler To: Remy Horton Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id C69315F72 for ; Wed, 25 Apr 2018 12:06:16 +0200 (CEST) In-Reply-To: <76bc7493-f8cf-0d74-961c-800665744ebe@intel.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" 25/04/2018 11:40, Remy Horton: > > On 24/04/2018 20:53, Thomas Monjalon wrote: > [..] > > But I would like to review the devargs you are standardizing. > > Unfortunately, I cannot find a documentation about it. > > How users are supposed to use it? > > Can you, at least, describe the syntax in the commit log, please? > > The patch follows this pseudo-BNF: > > cfg := pair (',' pair)* > pair := (key '=' value) > key := 'port' | 'representor' > value := range | list > range := int ('-' int)? > int := [0-9]+ > list := '[' range (',' range)* ']' OK Please can you add it as a comment in the parsing code? We will need one or two examples in the commit message too. Can you show a complete command line please? How do you give ethdev properties without the new devargs syntax (in progress by Gaetan)?