* [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support?
@ 2015-07-16 12:12 Rahul Lakkireddy
2015-07-16 7:57 ` David Marchand
0 siblings, 1 reply; 4+ messages in thread
From: Rahul Lakkireddy @ 2015-07-16 12:12 UTC (permalink / raw)
To: dev; +Cc: Kumar Sanghvi, Felix Marti, Nirranjan Kirubaharan
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support?
2015-07-16 12:12 [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support? Rahul Lakkireddy
@ 2015-07-16 7:57 ` David Marchand
2015-07-16 8:57 ` Bruce Richardson
0 siblings, 1 reply; 4+ messages in thread
From: David Marchand @ 2015-07-16 7:57 UTC (permalink / raw)
To: Rahul Lakkireddy; +Cc: dev, Felix Marti, Kumar Sanghvi, Nirranjan Kirubaharan
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
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support?
2015-07-16 7:57 ` David Marchand
@ 2015-07-16 8:57 ` Bruce Richardson
2015-07-16 11:12 ` Rahul Lakkireddy
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Richardson @ 2015-07-16 8:57 UTC (permalink / raw)
To: David Marchand; +Cc: dev, Nirranjan Kirubaharan, Felix Marti, Kumar Sanghvi
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
>
> --
> 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
> >
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support?
2015-07-16 8:57 ` Bruce Richardson
@ 2015-07-16 11:12 ` Rahul Lakkireddy
0 siblings, 0 replies; 4+ messages in thread
From: Rahul Lakkireddy @ 2015-07-16 11:12 UTC (permalink / raw)
To: Bruce Richardson, David Marchand
Cc: dev, Felix Marti, Kumar Sanghvi, Nirranjan Kirubaharan
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2015-07-16 11:12 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-16 12:12 [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support? Rahul Lakkireddy
2015-07-16 7:57 ` David Marchand
2015-07-16 8:57 ` Bruce Richardson
2015-07-16 11:12 ` Rahul Lakkireddy
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).