DPDK patches and discussions
 help / color / Atom feed
From: Rasesh Mody <rmody@marvell.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re:  [PATCH] doc: update qede PMD guide
Date: Fri, 22 Nov 2019 19:42:06 +0000
Message-ID: <BYAPR18MB283889C8815ABEE4238FE03CB5490@BYAPR18MB2838.namprd18.prod.outlook.com> (raw)
In-Reply-To: <fd53369e-07b5-4a52-be0b-444a13cb787b@intel.com>

Hi Ferruh,

>From: Ferruh Yigit <ferruh.yigit@intel.com>
>Sent: Friday, November 22, 2019 6:33 AM
>External Email
>On 11/22/2019 7:51 AM, Rasesh Mody wrote:
>>  - Add note for Co-existence of DPDK and Linux drivers.
>>  - Update the firmware version in example.
>>  - Add Config note for potential error due to lack of memzone desciptor
>>    count.
>> Signed-off-by: Rasesh Mody <rmody@marvell.com>
>> ---
>>  doc/guides/nics/qede.rst | 25 ++++++++++++++++++++-----
>>  1 file changed, 20 insertions(+), 5 deletions(-)
>> diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst index
>> 2f4045795..9c14dd006 100644
>> --- a/doc/guides/nics/qede.rst
>> +++ b/doc/guides/nics/qede.rst
>> @@ -70,6 +70,10 @@ Co-existence considerations
>>    to the PFs of a given adapter and either qede PMD or Linux drivers
>>    (qed and qede) can be bound to the VFs of the adapter.
>> +- To use DPDK on some PFs and Linux drivers on other PFs of an
>> +adapter,
>> +  create a VF each on the PFs where DPDK will be used, attach DPDK to
>> +  these VFs and Linux drivers to the other PFs where no VFs are created.
>But this won't be using DPDK on some PFs, you are indeed suggesting to
>create VFs and use them via DPDK instead. And should the PF not bound to
>any kernel driver?

For sharing an adapter between DPDK and Linux drivers, we are suggesting to use DPDK on a VF created on PFs. All the PFs would be bound to Linux drivers(qed/qede). I'll send out a v2 with modified text for more clarity.


  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  7:51 [dpdk-dev] " Rasesh Mody
2019-11-22 14:32 ` Ferruh Yigit
2019-11-22 19:42   ` Rasesh Mody [this message]
2019-11-22 23:31 ` [dpdk-dev] [PATCH v2] " Rasesh Mody
2019-11-25 15:32   ` Ferruh Yigit

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BYAPR18MB283889C8815ABEE4238FE03CB5490@BYAPR18MB2838.namprd18.prod.outlook.com \
    --to=rmody@marvell.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
	public-inbox-index dev

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox