From: Kevin Traynor <ktraynor@redhat.com>
To: Huisong Li <lihuisong@huawei.com>, stable@dpdk.org
Cc: liudongdong3@huawei.com, huangdaode@huawei.com, liuyonglong@huawei.com
Subject: Re: [PATCH 21.11 00/17] backport some patches for hns3
Date: Tue, 21 Mar 2023 16:21:50 +0000 [thread overview]
Message-ID: <95b81c41-fc6a-9c0f-0e07-31235c556615@redhat.com> (raw)
In-Reply-To: <20230321092306.16918-1-lihuisong@huawei.com>
On 21/03/2023 09:22, Huisong Li wrote:
> Some patches depends on the patch 13/17. So we also backport patch 13/17.
>
> Chengwen Feng (1):
> net/hns3: remove unused structures
>
> Huisong Li (16):
> net/hns3: separate Tx prepare from getting Tx function
> net/hns3: make getting Tx function static
> net/hns3: fix RSS key size compatibility
> net/hns3: fix burst mode query with dummy function
> net/hns3: extract common functions to set Rx/Tx
> net/hns3: use hardware config to report hash key
> net/hns3: use hardware config to report hash types
> net/hns3: separate setting hash algorithm
> net/hns3: separate setting hash key
> net/hns3: separate setting RSS types
> net/hns3: use new RSS rule to configure hardware
> net/hns3: save hash algo to RSS filter list node
> net/hns3: allow adding queue buffer size hash rule
> net/hns3: separate flow RSS config from RSS conf
> net/hns3: reimplement hash flow function
> net/hns3: add verification of RSS types
>
> drivers/net/hns3/hns3_cmd.h | 19 -
> drivers/net/hns3/hns3_common.c | 12 +-
> drivers/net/hns3/hns3_ethdev.c | 20 +-
> drivers/net/hns3/hns3_ethdev.h | 9 -
> drivers/net/hns3/hns3_ethdev_vf.c | 19 +-
> drivers/net/hns3/hns3_flow.c | 972 +++++++++++++++++++++---------
> drivers/net/hns3/hns3_flow.h | 23 +-
> drivers/net/hns3/hns3_mp.c | 4 +-
> drivers/net/hns3/hns3_rss.c | 563 ++++++++++++-----
> drivers/net/hns3/hns3_rss.h | 139 ++++-
> drivers/net/hns3/hns3_rxtx.c | 100 +--
> drivers/net/hns3/hns3_rxtx.h | 4 +-
> 12 files changed, 1289 insertions(+), 595 deletions(-)
>
Thanks Huisong. These are queued for 21.11 branch pending CI pass.
Kevin.
prev parent reply other threads:[~2023-03-21 16:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 9:22 Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 01/17] net/hns3: separate Tx prepare from getting Tx function Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 02/17] net/hns3: make getting Tx function static Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 03/17] net/hns3: fix RSS key size compatibility Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 04/17] net/hns3: fix burst mode query with dummy function Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 05/17] net/hns3: extract common functions to set Rx/Tx Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 06/17] net/hns3: use hardware config to report hash key Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 07/17] net/hns3: use hardware config to report hash types Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 08/17] net/hns3: separate setting hash algorithm Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 09/17] net/hns3: separate setting hash key Huisong Li
2023-03-21 9:22 ` [PATCH 21.11 10/17] net/hns3: separate setting RSS types Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 11/17] net/hns3: use new RSS rule to configure hardware Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 12/17] net/hns3: save hash algo to RSS filter list node Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 13/17] net/hns3: remove unused structures Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 14/17] net/hns3: allow adding queue buffer size hash rule Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 15/17] net/hns3: separate flow RSS config from RSS conf Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 16/17] net/hns3: reimplement hash flow function Huisong Li
2023-03-21 9:23 ` [PATCH 21.11 17/17] net/hns3: add verification of RSS types Huisong Li
2023-03-21 16:21 ` Kevin Traynor [this message]
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=95b81c41-fc6a-9c0f-0e07-31235c556615@redhat.com \
--to=ktraynor@redhat.com \
--cc=huangdaode@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stable@dpdk.org \
/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).