From: Rami Rosen <roszenrami@gmail.com>
To: jfargen@redhat.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] TestPMD testing with VMX3NET Devices...
Date: Fri, 7 Sep 2018 18:44:26 +0300 [thread overview]
Message-ID: <CAKoUAr=rKbYNXYEFv6OM215OFpYgX2DLPtZTZtfqB6efOnqqnw@mail.gmail.com> (raw)
In-Reply-To: <CAB-EjEJfguVL_8vWexG7M0QyBZBDkKzTHV1YnkXLGEynYC_f0Q@mail.gmail.com>
Hi Jamie,
>Ok, can you clear something else up. Should I use the vfio-pci or the igb_uio driver/kernel module?
Sure.
First there is a third option, which is binding with uio_pci_generic,
which is a generic kernel module.
When you bind with igb_uio, an entry called max_vfs will be generated
under the linux pci device sysfs entry.
Echoing an integer into max_vfs will generate DPDK VFs (if the DPDK
PMD support VFs; Intel and Mellnox
and other vendor nics do support it) as opposed to echoing into
sriov_numvs, which
generates a kernel module PF/PFs.
OTOH, You don't have max_vfs with vfio_pci and uio_pci_generic.
It says in the DPDK doc:
"If UEFI secure boot is enabled, the Linux kernel may disallow the use
of UIO on the system. Therefore, devices for use by DPDK should be
bound to the vfio-pci kernel module rather than igb_uio or
uio_pci_generic.'
see
http://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#vfio
see also:
"5.4. Binding and Unbinding Network Ports to/from the Kernel Modules":
http://doc.dpdk.org/guides/linux_gsg/linux_drivers.html#linux-gsg-binding-kernel
Hope this helps to clarify things,
Regards,
Rami Rosen
next prev parent reply other threads:[~2018-09-07 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 16:39 Jamie Fargen
2018-09-07 13:08 ` Rami Rosen
2018-09-07 13:22 ` Jamie Fargen
2018-09-07 13:52 ` Rami Rosen
2018-09-07 14:38 ` Jamie Fargen
2018-09-07 15:20 ` Jamie Fargen
2018-09-07 15:44 ` Rami Rosen [this message]
2018-09-07 17:24 ` Emre Eraltan
2018-09-07 18:06 ` Jamie Fargen
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='CAKoUAr=rKbYNXYEFv6OM215OFpYgX2DLPtZTZtfqB6efOnqqnw@mail.gmail.com' \
--to=roszenrami@gmail.com \
--cc=jfargen@redhat.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).