From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id B8A551B5C3 for ; Tue, 9 Oct 2018 19:11:29 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4FE9C220D7; Tue, 9 Oct 2018 13:11:29 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 09 Oct 2018 13:11:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=23qcOPvgUOhD9FM0/ug59kG7lYK4kaV96R4LLFmyvY8=; b=igfeWxRFHOyC VWfQjuXmmtf7VJIRgS/frPtCd7Bl+Jdt0aCwJw8zVjTdX0R6/FE8DbAZahY9O9H7 3QG9BVSE8bGemb3qWt6RNGNjLZn1Fq99xI+wYeOOOFH6AxY14oDOTdwVzgMUepsw VzchCSAMGfDCYVQlWGbGc5JdbJTpyXM= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=23qcOPvgUOhD9FM0/ug59kG7lYK4kaV96R4LLFmyv Y8=; b=cTGidGp7HuWlO8Nr2U0tYQ0HuzfLF1jKStgk0pjkNADun0WMilVnBdl46 K+7aW97a7wwVyLHkkZnruSmI0H2Pht7iN1pBT1PHCedz/Lpb6BeNKS83sG0jz40W KV5goDCJuMdNwys8CF5W9pGJe40eV+HMIzS0NqA5MIJulEd8pvOFLeOp9Qu1aq+7 E1lmJYE+87tcUXVngwkXewCnrRt6tiYhKB/EqQQFNhibSF4pXPII8LKXatAov+RN F4XoALvbiv2XI7Tkv6OO76RvKWwnxUsuxeR4bE3HoEE3r9gnfUpjJvwdvuSNgwxA kE0gMn6Iutg/8dkZi0qXBIoz6EG+A== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 3AE17102DD; Tue, 9 Oct 2018 13:11:27 -0400 (EDT) From: Thomas Monjalon To: Stephen Hemminger Cc: =?ISO-8859-1?Q?Ga=EBtan?= Rivet , dev@dpdk.org, ophirmu@mellanox.com, ferruh.yigit@intel.com, arybchenko@solarflare.com, olivier.matz@6wind.com, remy.horton@intel.com Date: Tue, 09 Oct 2018 19:11:25 +0200 Message-ID: <4748941.APsGkUoXuF@xps> In-Reply-To: <20181009081140.5c977ad6@xeon-e3> References: <20181009021858.19216-1-thomas@monjalon.net> <6562576.89BUxVsNiX@xps> <20181009081140.5c977ad6@xeon-e3> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH 1/4] kvargs: support list value X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Oct 2018 17:11:30 -0000 09/10/2018 17:11, Stephen Hemminger: > On Tue, 09 Oct 2018 16:31:24 +0200 > Thomas Monjalon wrote: >=20 > > 09/10/2018 16:14, Ga=EBtan Rivet: > > > Hi Thomas, > > >=20 > > > On Tue, Oct 09, 2018 at 04:18:55AM +0200, Thomas Monjalon wrote: =20 > > > > If a value contains a comma, rte_kvargs_tokenize() will split here. > > > > In order to support list syntax [a,b] as value, an extra parsing of > > > > the square brackets is added. > > > > =20 > > >=20 > > > Nice, I was actually planning to do this. > > >=20 > > > I think it could be useful to also support () and {}, as well as > > > recursive lists, but it is best to have a first version to support > > > representor and go from this. =20 > >=20 > > Yes, we have no usage of () and {} so far. >=20 > This is getting complex enough that doing a real parser maybe necessary. > Why not lex/yacc? I don't know how much it fits with our needs for devargs. > Or better yet go to real syntax like JSON. JSON is not suitable for one-line string as devargs.