From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Walter Heymans <walter.heymans@corigine.com>
Subject: Re: [PATCH v2 2/3] doc: update outdated information for the nfp PMD
Date: Mon, 20 Feb 2023 12:25:05 +0000 [thread overview]
Message-ID: <fb2d6cef-dee5-d1cf-1198-59c5d442a743@amd.com> (raw)
In-Reply-To: <20230220084111.40531-3-chaoyong.he@corigine.com>
On 2/20/2023 8:41 AM, Chaoyong He wrote:
> From: Walter Heymans <walter.heymans@corigine.com>
>
> Update nfp documentation with new information and remove outdated
> information. The most significant changes that are updated include:
> - Previously the NFP PMD did not support functionality to control VFs,
> it now does.
What I understand is DPDK supports VF but if PF is bound to Linux driver.
Previously support matrix was as following:
PF VF is supported
----- ---- --------------
Linux DPDK Yes
DPDK - Yes
DPDK DPDK NO
DPDK Linux ?No (not recommended)
Is PF:DPDK, VF:DPDK supported now?
This requires DPDK PF driver updated to manage VFs, if so can you please
list commits that adds this support in this commit log?
> - Previously the PF had to be bound to the kernel driver to create VFs,
> then VFs were created and bound to 'vfio-pci'. Currently it is
> possible to bind the PF to 'vfio-pci' and create VFs bound to
> 'vfio-pci'.
> - The name of the Linux kernel driver changed for VFs. Previously the
> 'nfp_netvf' module was used, but now both PFs and VFs use the 'nfp'
> module.
>
> Signed-off-by: Walter Heymans <walter.heymans@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
<...>
> @@ -209,8 +207,8 @@ vNIC service will keep polling packets from the firmware, and multiplex them
> to the corresponding representor port.
>
> In the Tx direction, the representor port will prepend the output port
> -information into metadata for each packet, and then send it to firmware through
> -PF vNIC.
> +information into metadata for each packet, and then send it to the firmware
> +through the PF vNIC.
>
Above change belongs to first patch.
next prev parent reply other threads:[~2023-02-20 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 8:08 [PATCH] doc: update NFP documentation with Corigine information Chaoyong He
2023-02-15 13:37 ` Ferruh Yigit
2023-02-15 17:58 ` Niklas Söderlund
2023-02-20 8:41 ` [PATCH v2 0/3] update NFP documentation Chaoyong He
2023-02-20 8:41 ` [PATCH v2 1/3] doc: wrap nfp doc to 80 characters and improve grammar Chaoyong He
2023-02-20 8:41 ` [PATCH v2 2/3] doc: update outdated information for the nfp PMD Chaoyong He
2023-02-20 12:25 ` Ferruh Yigit [this message]
2023-02-21 9:04 ` Chaoyong He
2023-02-21 9:29 ` Ferruh Yigit
2023-02-21 10:11 ` Chaoyong He
2023-02-21 10:42 ` Ferruh Yigit
2023-02-20 8:41 ` [PATCH v2 3/3] doc: add Corigine information to nfp documentation Chaoyong He
2023-02-22 1:23 ` [PATCH v2 0/3] update NFP documentation Ferruh Yigit
Reply instructions:
You may reply publicly 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=fb2d6cef-dee5-d1cf-1198-59c5d442a743@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=walter.heymans@corigine.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).