From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id EB492A10DA
	for <public@inbox.dpdk.org>; Wed, 31 Jul 2019 10:33:36 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 028811C132;
	Wed, 31 Jul 2019 10:33:36 +0200 (CEST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 8C90E1C0D6
 for <dev@dpdk.org>; Wed, 31 Jul 2019 10:33:33 +0200 (CEST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id 2DEAC223BA;
 Wed, 31 Jul 2019 04:33:33 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163])
 by compute1.internal (MEProxy); Wed, 31 Jul 2019 04:33:33 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 from:to:cc:subject:date:message-id:in-reply-to:references
 :mime-version:content-transfer-encoding:content-type; s=mesmtp;
 bh=50ErUqEil9BnGSx4wIwky6xvS2r1hgbmJl4PuA8dHeM=; b=aICODVAQGmiI
 zSpmStf+qIXMXoZc8ZuFEV7ZiSk69G0qOW+oybDFhWjZMktXOMQaL43UWsW+rVtR
 TcVQ+m7fD7gbKmiVmrt/vJUGNrswb7TJJVjV93d6bJ0CvS9muUNvkGpLXyF9csdn
 qGhs8IpCOZzMDhrPV1cPnXBLlV9oPk8=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
 :x-sasl-enc; s=fm3; bh=50ErUqEil9BnGSx4wIwky6xvS2r1hgbmJl4PuA8dH
 eM=; b=jqnIKWnimTikpe736OYsK8tVZg2mDRWGChO/xKTLSotrsIIxMPGZFvd/2
 o6m4S1hj5wXWS+gs9gyPw9r9G9TT53ExVo7Lh5sggvrs8meWnaMo224eENizqd/n
 rPhQZdoL0rG4HDJP0rwjf4abo+H6HGPhtc7Uq8WNKgxEPKjRxDR/BUiBpOCLCpQN
 2hQ12EH8LaPplAc6Mb+t4BzDz0dy+OlzoHXqLbI4WKR1cVDkcn/vp3kzszJSWqTR
 vFyiLPU+8jUO67/+hzeW7iQLDZIapqnbqJ31eldYYKbuu88bUcNQGi9sqnSQwbBW
 TCjntTVZ04S1Uc4TgrIxUOetc6WDg==
X-ME-Sender: <xms:XFJBXfQJ4zaP12l7W617Dq97LDGE_Z9B5ziDUNbxNB-W3QF4KKuhzg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleehgddthecutefuodetggdotefrodftvf
 curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu
 uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc
 fjughrpefhvffufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhmrghs
 ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph
 epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho
 mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgepud
X-ME-Proxy: <xmx:XFJBXep6YZf7VIsO-vEpiewvJKlb7Xziyx12X5bVB1QrO27_M5PBkQ>
 <xmx:XFJBXd4FffAWLfKwh6Kn1NM_5VzYObtCRrp2ugBhaaPfAjXsb0I2Vw>
 <xmx:XFJBXQRRO0C3G6KMUKgX_9cNA3Deel1vy4UE8Ht9XLgI9SXTE4Y15Q>
 <xmx:XVJBXTA_gE9J89FFtri4xGtxhL8mSje2FuBpqZLOooyYHpRsEywLXA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 0B01D380084;
 Wed, 31 Jul 2019 04:33:31 -0400 (EDT)
From: Thomas Monjalon <thomas@monjalon.net>
To: Rasesh Mody <rmody@marvell.com>
Cc: 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>
Date: Wed, 31 Jul 2019 10:33:29 +0200
Message-ID: <5892857.8Sh1EXfHd1@xps>
In-Reply-To: <20190731080225.19225-2-rmody@marvell.com>
References: <20190731080225.19225-1-rmody@marvell.com>
 <20190731080225.19225-2-rmody@marvell.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [dpdk-dev] [PATCH 2/2] doc: add a co-existence consideration
	for bnx2x PMD
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

31/07/2019 10:02, Rasesh Mody:
> Add and update co-existence considerations for bnx2x PMD
>=20
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> ---
>  doc/guides/nics/bnx2x.rst | 15 ++++++++++++---
>  1 file changed, 12 insertions(+), 3 deletions(-)
>=20
> 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.
> =20
> -- 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=E2=80=99t be mixed on a given B=
CM578xx
> +  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.