[dpdk-dev] [PATCH 2/2] doc: add a co-existence consideration for bnx2x PMD

[Thomas Monjalon]

31/07/2019 10:02, Rasesh Mody:
> Add and update co-existence considerations for bnx2x PMD
> 
> Signed-off-by: Rasesh Mody <rmody at 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.