From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rahul Lakkireddy Subject: Re: Does FreeBSD's nic_uio have bind/unbind interface support? Date: Thu, 16 Jul 2015 16:42:06 +0530 Message-ID: <20150716111203.GA3535@scalar.blr.asicdesigners.com> References: <20150716121214.GA3103@scalar.blr.asicdesigners.com> <20150716085714.GA9348@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" , Felix Marti , Kumar Sanghvi , Nirranjan Kirubaharan To: Bruce Richardson , David Marchand Return-path: Received: from stargate3.asicdesigners.com (stargate.chelsio.com [67.207.112.58]) by dpdk.org (Postfix) with ESMTP id 1C9C7CE7 for ; Thu, 16 Jul 2015 13:12:37 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20150716085714.GA9348@bricha3-MOBL3> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Bruce and David, On Thu, Jul 16, 2015 at 09:57:15 +0100, Bruce Richardson wrote: > On Thu, Jul 16, 2015 at 09:57:03AM +0200, David Marchand wrote: > > Hello Rahul, > > > > (cc Bruce) > > > > How about removing this "whitelist" from the nic_uio driver and just rely > > on the hw.nic_uio.bdfs parameter to find out which devices to bind ? > > > Yes, that would be my thinking too. It probably should work that way, much as > linux does. > > /Bruce > Tried the suggestion on removing the "whitelist" checks and it seems to work fine for us. It's allowing T5 devices to be bound to nic_uio and also results in successful probe. Will prepare a patch to remove the whitelist checks and pci id entries from nic_uio and post soon. Thanks, Rahul