From: Qiming Yang <qiming.yang@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, jingjing.wu@intel.com,
Qiming Yang <qiming.yang@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add VF support statement
Date: Tue, 18 Apr 2017 13:36:21 +0800 [thread overview]
Message-ID: <1492493781-33501-1-git-send-email-qiming.yang@intel.com> (raw)
This patch adds two note in doc build_dpdk, suggests DPDK user
don't use ``vfio-pci`` and ``uio_pci_generic`` module to create
virtual functions(VFs).
Signed-off-by: Qiming Yang <qiming.yang@intel.com>
---
doc/guides/linux_gsg/build_dpdk.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/linux_gsg/build_dpdk.rst b/doc/guides/linux_gsg/build_dpdk.rst
index 9d24573..b79ca48 100644
--- a/doc/guides/linux_gsg/build_dpdk.rst
+++ b/doc/guides/linux_gsg/build_dpdk.rst
@@ -155,6 +155,10 @@ can provide the uio capability. This module can be loaded using the command
sudo modprobe uio_pci_generic
+.. note::
+
+ ``uio_pci_generic`` module doesn't support to create virtual functions.
+
As an alternative to the ``uio_pci_generic``, the DPDK also includes the igb_uio
module which can be found in the kmod subdirectory referred to above. It can
be loaded as shown below:
@@ -187,6 +191,10 @@ however please consult your distributions documentation to make sure that is the
Also, to use VFIO, both kernel and BIOS must support and be configured to use IO virtualization (such as Intel® VT-d).
+.. note::
+
+ ``vfio-pci`` module doesn't support to create virtual functions.
+
For proper operation of VFIO when running DPDK applications as a non-privileged user, correct permissions should also be set up.
This can be done by using the DPDK setup script (called dpdk-setup.sh and located in the usertools directory).
--
2.7.4
next reply other threads:[~2017-04-18 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 5:36 Qiming Yang [this message]
2017-04-26 15:07 ` Mcnamara, John
2017-05-03 6:21 ` [dpdk-dev] [PATCH v2] " Qiming Yang
2017-05-07 12:16 ` Thomas Monjalon
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=1492493781-33501-1-git-send-email-qiming.yang@intel.com \
--to=qiming.yang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.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).