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 358AE1B106 for ; Thu, 20 Sep 2018 18:11:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CB56A21D06; Thu, 20 Sep 2018 12:11:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 20 Sep 2018 12:11:46 -0400 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=LsWjFf94sLGNCt2T0iRPmPAacX suoRt2XahRh8NaCvk=; b=fIOckkrpb2wwmuZDcUsW8RJ20+rGNDuZCMSDAIzCxd zEExx8w822K2ww1LiLcjCaBuSfMb79abJeUZG5PXw8WfJszuKicPmL655Y3jfZtu mDCtOPQ7rHv1a/YFakyt3EYDGKpVeHRYF20ia7XpoTM71/SGzzgVHoBnpw1lEyx9 o= 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=fm3; bh=LsWjFf 94sLGNCt2T0iRPmPAacXsuoRt2XahRh8NaCvk=; b=luzcQVrbC4z57fQqi0CKYh XBzIl2CvJSot7l09vLzhNvkJaeyIi5uPRItz7cA9D3dpefYr+jVMnZyyIgnPRQ6M DdSEeiCz4VyaoulL3UkOPqwEAvViwuKdjp2RzUFpf8JEYAX2gFntos346zArwu1l bR6tdO/iHXenQXfVUJWHyL/aouUY5BqzG2GOMLBPhAcKOhPfpjvyKflQuk1YfqQE YlWr4GjVfWtPNnYA3Utmyn4qOsu+Le73lttIyTvGk73mC/bJBQcz3plnCEAy2O+r lohcm3oVFuR8EQ6beJnFz2FmCT/aSkX3JFKLPqLWcdOd1syVjA3Tl4Fl6cQNZzjw == X-ME-Proxy: 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 E733D102E5; Thu, 20 Sep 2018 12:11:45 -0400 (EDT) From: Thomas Monjalon To: Gaetan Rivet Cc: dev@dpdk.org Date: Thu, 20 Sep 2018 18:11:44 +0200 Message-ID: <2305853.Xkr2rJqqKv@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 04/13] bus/vdev: add device matching field driver 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, 20 Sep 2018 16:11:47 -0000 19/09/2018 18:03, Gaetan Rivet: > The vdev bus parses a field "driver", matching > a vdev driver name with one passed as follows: > > "bus=vdev,driver=xxxx" I think the property should be "name". We already have a "driver" category. So it may be "bus=vdev,name=mytap/driver=tap" Until now we were using the name of the driver as a prefix for the device name because it was the only way of knowing the driver to use. With a richer syntax like above, this restriction can be removed.