From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 7B3961B021 for ; Thu, 18 Jan 2018 09:47:04 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CDC3920BF6; Thu, 18 Jan 2018 03:47:03 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 18 Jan 2018 03:47:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=fLqPYV4Mpn65hDNTeo7MRrytHA 553iEYwDTRXnRd92U=; b=sIfVSWS4Dxa4UbOXT+fW5AbGZwl7pMDb0gSvaucAru /FgVRg5g1BABMQSiN4Zki2Nwanfj6W9cTg8puQZKBHRKdM0kKs0idaLxZzai/Jsg OygYTy5tEqZWtN5pt5qHmtkE1EpxY99JhSp6C48d7lQkfGjk5giHweL9JBKSBPo5 M= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=fLqPYV 4Mpn65hDNTeo7MRrytHA553iEYwDTRXnRd92U=; b=bQfm3/0OwxCXFzdU1Y08UH uw3ABR1aiGLmY1RYcZCxFCAMjq/se+6vjw8X3VoyAlM8VSkeMkA11b/P5UWT0JgR qyq+qN2CsK+NOSJtv6iMe8YWZkMxLpYZWbrrj3NsagACr5V0HHkjuat62PupPBQZ dWGO2YaKhfr+1Ff/ZvoFuuOqmGxvnETEV2yJNUY4do0UCWmM1onXZPl1R3uYGnYn QsmTg2so6dgAV1TDmj606PmPi4/AMsfvfiFmW7traQ+GeXsbQOcxrSfE4DvQFiEm +o4rUnNpdfqC6tQUGDvoQ3HPZJM/WghTXp0J/lcOqceLSpUzBrk1S0o2EJDfRQIg == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 77928240DE; Thu, 18 Jan 2018 03:47:03 -0500 (EST) From: Thomas Monjalon To: Yuanhan Liu , Ferruh Yigit Cc: dev@dpdk.org Date: Thu, 18 Jan 2018 09:46:29 +0100 Message-ID: <1649717.sl7PR1QSdr@xps> In-Reply-To: <20180118073520.GZ29540@yliu-mob> References: <1516114218-21501-1-git-send-email-yliu@fridaylinux.org> <68453aa8-de09-c41b-0b84-82eb6bbe19ac@intel.com> <20180118073520.GZ29540@yliu-mob> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: document the new devargs syntax 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: Thu, 18 Jan 2018 08:47:04 -0000 18/01/2018 08:35, Yuanhan Liu: > On Wed, Jan 17, 2018 at 12:34:08PM +0000, Ferruh Yigit wrote: > > So does it make sense to separate them logically? Perhaps as "device identifier" > > and "device args". > > Then I think it returns back to the old issue: how could we identify a > port when the bus id (say BDF for PCI bus) is not enough for identifying > a port? Such case could happen when a single NIC has 2 ports sharing > the same BDF. It could also happen with the VF representors that will > be introduced shortly. Yes, the device matching syntax must include bus category, class category and driver category. So any device can be identified in future. But I think Ferruh is talking about separating device matching (which is described in this proposal) and device settings (which are usually mixed in -w and --vdev options). I agree there are different things and may be separate. They could share the same syntax (bus/class/driver) but be separate with a semicolon: matching;settings