From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f173.google.com (mail-ob0-f173.google.com [209.85.214.173]) by dpdk.org (Postfix) with ESMTP id 8B3D05A86 for ; Thu, 16 Jul 2015 09:57:04 +0200 (CEST) Received: by obbop1 with SMTP id op1so42167575obb.2 for ; Thu, 16 Jul 2015 00:57:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=MoTOAm5f+4bnyC9NOgEkLAExG8rGehz3cmizhNc8R8U=; b=RTadm7zzwyKGiPvSbzjVsfr7dS1yyoYDKUzhgk3YaA+Pt4bNwteKJDg+nfNAyBGpNq ksstqDCuTvftw73PefloRHqvv6/rumES46cySRbTNsPx+AuePDaj00u/PN/N1zXMXTd+ Vz1vtS8hgZexB4/K8037umTvibPQ7MB7ZWC83AXWsusgZia9O6i6wZaz3Hf8sKDkzG3x JKb8WJ9kD0euGo/qLcNcXkHnDJwZ7Ooj2K3VGIQK9kqBR2dlA7qqEMH1XDFkTVZyhlGr 4XWJnUZmtzJa3VZq045nzRLmu/BJrx5G9VjZa58brXi80VmsnbNg1UIPMZe5pjK6M8b/ b2vg== X-Gm-Message-State: ALoCoQnXF71CV1iPZ0dMSl9MBQy3ULXGGlQ9Jds+pvYDig+ww5TesTDXK3mbI8pl7zaT+H2wVlDq MIME-Version: 1.0 X-Received: by 10.182.29.33 with SMTP id g1mr7864731obh.72.1437033423668; Thu, 16 Jul 2015 00:57:03 -0700 (PDT) Received: by 10.76.84.233 with HTTP; Thu, 16 Jul 2015 00:57:03 -0700 (PDT) In-Reply-To: <20150716121214.GA3103@scalar.blr.asicdesigners.com> References: <20150716121214.GA3103@scalar.blr.asicdesigners.com> Date: Thu, 16 Jul 2015 09:57:03 +0200 Message-ID: From: David Marchand To: Rahul Lakkireddy Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" , Felix Marti , Kumar Sanghvi , Nirranjan Kirubaharan Subject: Re: [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support? X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2015 07:57:05 -0000 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 ? -- David Marchand On Thu, Jul 16, 2015 at 2:12 PM, Rahul Lakkireddy < rahul.lakkireddy@chelsio.com> wrote: > Hi All, > > It seems that on FreeBSD, nic_uio currently only binds the devices matched > in > rte_pci_dev_ids.h. On Linux, it's possible to bind any listed device with > igb_uio or vfio. > > The pci device ids supported by cxgbe PMD, maintained in a table, are not > part > of rte_pci_dev_ids.h. Hence, Chelsio T5 cards don't get bound to nic_uio, > resulting in probe failure on FreeBSD. > > On manually adding Chelsio pci device id to rte_pci_dev_ids.h, the Chelsio > T5 > card gets detected fine on FreeBSD. > > So, we would like to know and understand if adding all supported Chelsio > pci > device ids to rte_pci_dev_ids.h is the correct way of doing things for > FreeBSD? > > Any suggestions are appreciated. > > Thanks, > Rahul >