From: Rasesh Mody <rmody@marvell.com>
To: <dev@dpdk.org>
Cc: Rasesh Mody <rmody@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: [dpdk-dev] [PATCH] doc: add a co-existence consideration for qede PMD
Date: Wed, 31 Jul 2019 01:02:07 -0700 [thread overview]
Message-ID: <20190731080207.19167-1-rmody@marvell.com> (raw)
Add and update co-existence considerations for qede PMD
Signed-off-by: Rasesh Mody <rmody@marvell.com>
---
doc/guides/nics/qede.rst | 21 +++++++++++++++++++--
1 file changed, 19 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst
index c0a383381..87cf989c1 100644
--- a/doc/guides/nics/qede.rst
+++ b/doc/guides/nics/qede.rst
@@ -47,8 +47,25 @@ Non-supported Features
Co-existence considerations
---------------------------
-- QLogic FastLinQ QL4xxxx CNAs can have both NIC and Storage personalities. However, coexistence with storage protocol drivers (qedi and qedf) is not supported on the same adapter. So storage personality has to be disabled on that adapter when used in DPDK applications.
-- For SR-IOV case, qede PMD will be used to bind to SR-IOV VF device and Linux native kernel driver (qede) will be attached to SR-IOV PF.
+
+- QLogic FastLinQ QL4xxxx CNAs can have both NIC and Storage
+ personalities. However, coexistence with storage protocol drivers
+ (qedi and qedf) is not supported on the same adapter. So storage
+ personality has to be disabled on that adapter when used in DPDK
+ applications.
+
+- Linux kernel drivers and qede PMD can’t be mixed on a given FastLinQ
+ QL4xxx adapter. This type of coexistence is unsupported. A given
+ adapter needs to be completely used by DPDK or Linux drivers, when
+ SR-IOV is not enabled. Before binging DPDK driver to one or more
+ devices on the adapter, please make sure to unbind Linux drivers from
+ all devices of the adapter. If there are multiple adapters on the
+ system, one or more adapter can be used by DPDK driver and other
+ adapters can be used by Linux drivers.
+
+- When SR-IOV is enabled, Linux native kernel driver (qede) can be bound
+ to the PFs of a given adapter and either DPDK or Linux drivers can be
+ bound to the VFs of the adapter.
Supported QLogic Adapters
-------------------------
--
2.18.0
next reply other threads:[~2019-07-31 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 8:02 Rasesh Mody [this message]
2019-07-31 8:31 ` Thomas Monjalon
2019-08-05 9:26 ` Rasesh Mody
2019-08-05 10:16 ` Thomas Monjalon
2019-08-05 9:19 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2019-08-05 15:26 ` Jerin Jacob Kollanukkaran
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=20190731080207.19167-1-rmody@marvell.com \
--to=rmody@marvell.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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).