From: David Marchand <david.marchand@redhat.com>
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: how to bind VF interface into dpdk
Date: Thu, 15 Sep 2022 09:22:51 +0200 [thread overview]
Message-ID: <CAJFAV8wtO0o1P3_+vFKfhHwXTLpfQ9aKmkEc1PQA40Z0zfAc+g@mail.gmail.com> (raw)
In-Reply-To: <PSAPR04MB5516D1636A4D162097532641D6469@PSAPR04MB5516.apcprd04.prod.outlook.com>
On Wed, Sep 14, 2022 at 2:30 PM Balakrishnan K
<Balakrishnan.K1@tatacommunications.com> wrote:
>
> I am trying to bind VF interface to dpdk using dpdk-devbind.py.
>
> Unable to bind getting error “cannot bind to driver uio_pci_generic”.
>
> Steps followed:
>
> 1.modprobe uio_pci_generic
>
> 2. dpdk-devbind.py -b uio_pci_generic 0000:05:00.0
In general, you should use vfio-pci.
Now, for your particular case, ixgbe VF devices (10ed) won't work with
uio_pci_generic, and it is reported in the driver info.
$ ./usertools/dpdk-pmdinfo.py build-gcc/drivers/librte_net_ixgbe.so | less
PMD NAME: net_ixgbe_vf
PMD PARAMETERS: pflink_fullchk=<0|1>
PMD KMOD DEPENDENCIES: * igb_uio | vfio-pci
PMD HW SUPPORT:
Intel Corporation (8086) : 82599 Ethernet Controller Virtual Function
(10ed) (All Subdevices)
Intel Corporation (8086) : 82599 Virtual Function (152e) (All Subdevices)
Intel Corporation (8086) : X540 Ethernet Controller Virtual Function
(1515) (All Subdevices)
Intel Corporation (8086) : X540 Virtual Function (1530) (All Subdevices)
Intel Corporation (8086) : X550 Virtual Function (1564) (All Subdevices)
Intel Corporation (8086) : X550 Virtual Function (1565) (All Subdevices)
Intel Corporation (8086) : X553 Virtual Function (15c5) (All Subdevices)
Intel Corporation (8086) : X553 Virtual Function (15b4) (All Subdevices)
Intel Corporation (8086) : Ethernet Connection X552 Virtual Function
(15a8) (All Subdevices)
Intel Corporation (8086) : X552 Virtual Function (15a9) (All Subdevices)
...
>
> Also tried with vfio-pci driver not succeeded.
We need dmesg output in this case, to be sure.
In general, it means that either your system has no iommu (there is a
special *unsafe* mode, for handling this case), or the iommu is not
configured.
Please see https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#vfio
--
David Marchand
prev parent reply other threads:[~2022-09-15 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 12:30 Balakrishnan K
2022-09-15 2:30 ` Satish Patel
2022-09-15 7:12 ` Balakrishnan K
2022-09-15 7:22 ` David Marchand [this message]
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=CAJFAV8wtO0o1P3_+vFKfhHwXTLpfQ9aKmkEc1PQA40Z0zfAc+g@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Balakrishnan.K1@tatacommunications.com \
--cc=users@dpdk.org \
/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).