From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A8AEDA10DA for ; Wed, 31 Jul 2019 10:31:33 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 73ADA1C0D6; Wed, 31 Jul 2019 10:31:33 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 21BFE1C06D for ; Wed, 31 Jul 2019 10:31:32 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B1BAD2208A; Wed, 31 Jul 2019 04:31:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 31 Jul 2019 04:31:31 -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=80YCdgITwN3OAxcI9XW6GXNV5Y2aghiv5ROCWlg1BFM=; b=sjoIwIFoQQ3f KrWMMvcqwh49wK8nHLrJ6BfO9ov4Naa912IIOYv5goCoSi7oXq5NN55urmYxe6YY Dx3eGs4kYYQKN3O0MwgwlfowlDTXik1+xgdFlp0EOqPOwlLlOOzElUI+cWbDCKHR yGgWCz/u/i8OmNExUSu40WWhvDsRbTs= 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=80YCdgITwN3OAxcI9XW6GXNV5Y2aghiv5ROCWlg1B FM=; b=i7pZyCH3L8HT6HWg3zvYMJpdceN0NhDfVoVEjUI3FLz7BJFIc1+AU+6JL QhKE6Q/yfgkV0TejRGGMa6UnsZzv6LTzXd3d+M7b0QShn6z0tamGlfzEziwP8o84 +vGCpsXwkc2EdUp86K9vVMq6Ks+pC68HwMQu2O/Pgp5XZOAhaoOVsR1HszDXBPuH hqlcizZqI0V6L6FsThx2TZTPtPXQkPbEE18lpS1fGr/ZVC8pptXna4BWdIGNO0Af LIjczt6R8VzFPi/P9GkKI5Q2U9qqDNcEM7FimCMtL6nszZC1FG71zoZJmxRl9/xD EyCbPsYZUQcvx6N1x7b1kkvZWPNuw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrleehgddthecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A6BC5380083; Wed, 31 Jul 2019 04:31:30 -0400 (EDT) From: Thomas Monjalon To: Rasesh Mody Cc: dev@dpdk.org, John McNamara , Jerin Jacob Kollanukkaran , GR-Everest-DPDK-Dev Date: Wed, 31 Jul 2019 10:31:27 +0200 Message-ID: <5679747.Mjy3nje23Q@xps> In-Reply-To: <20190731080207.19167-1-rmody@marvell.com> References: <20190731080207.19167-1-rmody@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH] doc: add a co-existence consideration for qede PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 31/07/2019 10:02, Rasesh Mody: > Add and update co-existence considerations for qede PMD >=20 > Signed-off-by: Rasesh Mody > --- > doc/guides/nics/qede.rst | 21 +++++++++++++++++++-- > 1 file changed, 19 insertions(+), 2 deletions(-) >=20 > +- Linux kernel drivers and qede PMD can=E2=80=99t be mixed on a given Fa= stLinQ > + 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. This part is not specific to qede, but related to UIO/VFIO behaviour. I think we already have this kind of explanation in the Linux guide. If not, please update it and add a reference link from here. Thanks