From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2 02/42] eal: parse "driver" device argument before probing drivers Date: Wed, 10 May 2017 12:01:53 +0100 Message-ID: <21031bf2-9472-c0c9-a344-4ce955e795c1@intel.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Gaetan Rivet , Jan Blunck Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id D72E12952 for ; Wed, 10 May 2017 13:01:55 +0200 (CEST) In-Reply-To: Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 5/10/2017 3:34 AM, Ferruh Yigit wrote: > On 4/11/2017 4:44 PM, Gaetan Rivet wrote: >> From: Jan Blunck >> >> In some cases the virtual device name should be totally different than >> the driver being used for the device. Therefore lets parse the devargs for >> the "driver" argument before probing drivers in vdev_probe_all_drivers(). > > Hi Gaetan, Jan, > > I have caught this while checking something else. > > This patch adds an alternative way for virtual devices to get probed > when device name is not proper. > > This probing can be done by having "driver=" in device > argument (not in name). > > Do we really need this alternative method, as far as I can see only user > of this is a unit test for bonding? > > This method is a little hidden/undocumented and a hack solution, I think > it is better and easier to fix virtual device names in unit test and > remove this, what do you think? I am suggesting: http://dpdk.org/dev/patchwork/patch/24196/ > > Thanks, > ferruh > >> >> Signed-off-by: Jan Blunck > <...> >