From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: dev@dpdk.org
Cc: Kumar Sanghvi <kumaras@chelsio.com>,
Felix Marti <felix@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>
Subject: [dpdk-dev] Does FreeBSD's nic_uio have bind/unbind interface support?
Date: Thu, 16 Jul 2015 17:42:16 +0530 [thread overview]
Message-ID: <20150716121214.GA3103@scalar.blr.asicdesigners.com> (raw)
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
next reply other threads:[~2015-07-16 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 12:12 Rahul Lakkireddy [this message]
2015-07-16 7:57 ` David Marchand
2015-07-16 8:57 ` Bruce Richardson
2015-07-16 11:12 ` Rahul Lakkireddy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150716121214.GA3103@scalar.blr.asicdesigners.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=dev@dpdk.org \
--cc=felix@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=nirranjan@chelsio.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).