From: Ferruh Yigit <ferruh.yigit@amd.com>
To: beilei.xing@intel.com, jingjing.wu@intel.com
Cc: dev@dpdk.org, Qi Z Zhang <qi.z.zhang@intel.com>
Subject: Re: [PATCH] doc: update feature list for idpf and cpfl
Date: Fri, 13 Oct 2023 12:45:35 +0100 [thread overview]
Message-ID: <f639518d-faec-4f53-a1cf-92e91db80896@amd.com> (raw)
In-Reply-To: <20231012151542.463873-1-beilei.xing@intel.com>
On 10/12/2023 4:15 PM, beilei.xing@intel.com wrote:
> From: Beilei Xing <beilei.xing@intel.com>
>
> Add RSS support in idpf.ini and cpfl.ini.
>
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> ---
> doc/guides/nics/features/cpfl.ini | 3 +++
> doc/guides/nics/features/idpf.ini | 3 +++
> 2 files changed, 6 insertions(+)
>
> diff --git a/doc/guides/nics/features/cpfl.ini b/doc/guides/nics/features/cpfl.ini
> index f4e45c7c68..4eb1c829cc 100644
> --- a/doc/guides/nics/features/cpfl.ini
> +++ b/doc/guides/nics/features/cpfl.ini
> @@ -9,6 +9,9 @@
> [Features]
> MTU update = Y
> TSO = P
> +RSS hash = Y
> +RSS key update = Y
> +RSS reta update = Y
> L3 checksum offload = P
> L4 checksum offload = P
> Linux = Y
> diff --git a/doc/guides/nics/features/idpf.ini b/doc/guides/nics/features/idpf.ini
> index 099fd7f216..d004681c3a 100644
> --- a/doc/guides/nics/features/idpf.ini
> +++ b/doc/guides/nics/features/idpf.ini
> @@ -9,6 +9,9 @@
> [Features]
> MTU update = Y
> TSO = P
> +RSS hash = Y
> +RSS key update = Y
> +RSS reta update = Y
> L3 checksum offload = P
> L4 checksum offload = P
> Timestamp offload = P
Thanks Beilei, for RSS hash feature update,
but both driver has still very small set of feature list, I didn't check
the details but is this the feature list complete? Can you please double
check?
Thanks,
ferruh
next prev parent reply other threads:[~2023-10-13 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 15:15 beilei.xing
2023-10-13 11:45 ` Ferruh Yigit [this message]
2023-10-17 13:25 ` [PATCH v2] " beilei.xing
2023-11-01 0:59 ` Zhang, Qi Z
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=f639518d-faec-4f53-a1cf-92e91db80896@amd.com \
--to=ferruh.yigit@amd.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.zhang@intel.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).