From: Rasesh Mody <rmody@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
John McNamara <john.mcnamara@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add a co-existence consideration for bnx2x PMD
Date: Mon, 5 Aug 2019 09:28:58 +0000 [thread overview]
Message-ID: <BYAPR18MB28388502AE942F3059A4E64BB5DA0@BYAPR18MB2838.namprd18.prod.outlook.com> (raw)
In-Reply-To: <5892857.8Sh1EXfHd1@xps>
>From: Thomas Monjalon <thomas@monjalon.net>
>Sent: Wednesday, July 31, 2019 1:33 AM
>
>31/07/2019 10:02, Rasesh Mody:
>> Add and update co-existence considerations for bnx2x PMD
>>
>> Signed-off-by: Rasesh Mody <rmody@marvell.com>
>> ---
>> doc/guides/nics/bnx2x.rst | 15 ++++++++++++---
>> 1 file changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/doc/guides/nics/bnx2x.rst b/doc/guides/nics/bnx2x.rst
>> index a7dee0c10..358ed7927 100644
>> --- a/doc/guides/nics/bnx2x.rst
>> +++ b/doc/guides/nics/bnx2x.rst
>> @@ -69,9 +69,18 @@ Co-existence considerations
>> bnx2fi) 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, bnx2x PMD will be used to bind to SR-IOV VF device
>> and
>> - Linux native kernel driver (bnx2x) will be attached to SR-IOV PF.
>> -
>> +- Linux kernel drivers and bnx2x PMD can’t be mixed on a given
>> +BCM578xx
>> + 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 (bnx2x) 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.
>
>Same comment as for qede: this is not specific to the PMD.
>Please update and reference the Linux guide.
Please see the v2 set with documentation specific to QLogic adapters and use of bnx2x PMD.
Thanks!
-Rasesh
next prev parent reply other threads:[~2019-08-05 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 8:02 [dpdk-dev] [PATCH 1/2] doc: use SPDX tag for bnx2x PMD guide Rasesh Mody
2019-07-31 8:02 ` [dpdk-dev] [PATCH 2/2] doc: add a co-existence consideration for bnx2x PMD Rasesh Mody
2019-07-31 8:33 ` Thomas Monjalon
2019-08-05 9:28 ` Rasesh Mody [this message]
2019-07-31 11:39 ` Shahed Shaikh
2019-07-31 8:09 ` [dpdk-dev] [PATCH 1/2] doc: use SPDX tag for bnx2x PMD guide Rasesh Mody
2019-08-05 9:24 ` [dpdk-dev] [PATCH v2 " Rasesh Mody
2019-08-05 15:25 ` Jerin Jacob Kollanukkaran
2019-08-05 9:24 ` [dpdk-dev] [PATCH v2 2/2] doc: add a co-existence consideration for bnx2x PMD Rasesh Mody
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=BYAPR18MB28388502AE942F3059A4E64BB5DA0@BYAPR18MB2838.namprd18.prod.outlook.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).