From: Dengdui Huang <huangdengdui@huawei.com>
To: <dev@dpdk.org>
Cc: <stephen@networkplumber.org>, <lihuisong@huawei.com>,
<fengchengwen@huawei.com>, <liuyonglong@huawei.com>
Subject: [PATCH 0/6] net/hns3: VF support multi-TCs
Date: Wed, 11 Jun 2025 16:18:54 +0800 [thread overview]
Message-ID: <20250611081900.3658421-1-huangdengdui@huawei.com> (raw)
This patchset adds the VF multi-TCs feature.
Chengwen Feng (6):
net/hns3: fix VF fail to config queue TC
net/hns3: remove duplicate struct field
net/hns3: refactor DCB module code
net/hns3: VF support parse max TC number
net/hns3: VF support discover multi-TCs capability
net/hns3: VF support multi-TCs configure
drivers/net/hns3/hns3_cmd.c | 5 +-
drivers/net/hns3/hns3_cmd.h | 10 +
drivers/net/hns3/hns3_dcb.c | 161 ++++++++++++----
drivers/net/hns3/hns3_dcb.h | 4 +
drivers/net/hns3/hns3_dump.c | 11 +-
drivers/net/hns3/hns3_ethdev.c | 132 ++-----------
drivers/net/hns3/hns3_ethdev.h | 12 +-
drivers/net/hns3/hns3_ethdev_vf.c | 297 ++++++++++++++++++++++++++++--
drivers/net/hns3/hns3_mbx.h | 50 ++++-
drivers/net/hns3/hns3_rss.c | 8 +-
drivers/net/hns3/hns3_rxtx.c | 26 ++-
drivers/net/hns3/hns3_tm.c | 6 +-
12 files changed, 539 insertions(+), 183 deletions(-)
--
2.33.0
next reply other threads:[~2025-06-11 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 8:18 Dengdui Huang [this message]
2025-06-11 8:18 ` [PATCH 1/6] net/hns3: fix VF fail to config queue TC Dengdui Huang
2025-06-11 8:18 ` [PATCH 2/6] net/hns3: remove duplicate struct field Dengdui Huang
2025-06-11 8:18 ` [PATCH 3/6] net/hns3: refactor DCB module code Dengdui Huang
2025-06-11 8:18 ` [PATCH 4/6] net/hns3: VF support parse max TC number Dengdui Huang
2025-06-11 8:18 ` [PATCH 5/6] net/hns3: VF support discover multi-TCs capability Dengdui Huang
2025-06-11 8:19 ` [PATCH 6/6] net/hns3: VF support multi-TCs configure Dengdui Huang
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=20250611081900.3658421-1-huangdengdui@huawei.com \
--to=huangdengdui@huawei.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=stephen@networkplumber.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).