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

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?

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22  7:51 Rasesh Mody
2019-11-22 14:32 ` Ferruh Yigit [this message]
2019-11-22 19:42   ` [dpdk-dev] [EXT] " Rasesh Mody
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:
  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=fd53369e-07b5-4a52-be0b-444a13cb787b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=rmody@marvell.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

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 \
		dev@dpdk.org
	public-inbox-index dev


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


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