From: Dongdong Liu <liudongdong3@huawei.com>
To: <dev@dpdk.org>, <andrew.rybchenko@oktetlabs.ru>,
<ferruh.yigit@xilinx.com>, <thomas@monjalon.net>
Cc: <stable@dpdk.org>, Dongdong Liu <liudongdong3@huawei.com>
Subject: [PATCH 0/8] some bugfixes for hns3
Date: Wed, 27 Jul 2022 18:36:08 +0800 [thread overview]
Message-ID: <20220727103616.18596-1-liudongdong3@huawei.com> (raw)
The patchset include some bugfixes for hns3.
Chengwen Feng (6):
net/hns3: fix segment fault when using SVE xmit
net/hns3: fix next-to-use overflow when using SVE xmit
net/hns3: fix next-to-use overflow when using simple xmit
net/hns3: optimize SVE xmit performance
net/hns3: fix segment fault when secondary process access FW
net/hns3: revert optimize Tx performance
Huisong Li (2):
net/hns3: delete rte unused tag
net/hns3: fix uncleared hardware MAC statistics
drivers/net/hns3/hns3_ethdev.c | 10 ++-
drivers/net/hns3/hns3_ethdev_vf.c | 11 ++-
drivers/net/hns3/hns3_rxtx.c | 123 ++++++++++++++-------------
drivers/net/hns3/hns3_rxtx_vec_sve.c | 32 +++----
drivers/net/hns3/hns3_stats.c | 26 ++----
5 files changed, 109 insertions(+), 93 deletions(-)
--
2.22.0
next reply other threads:[~2022-07-27 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 10:36 Dongdong Liu [this message]
2022-07-27 10:36 ` [PATCH 1/8] net/hns3: fix segment fault when using SVE xmit Dongdong Liu
2022-07-27 10:36 ` [PATCH 2/8] net/hns3: fix next-to-use overflow " Dongdong Liu
2022-07-27 10:36 ` [PATCH 3/8] net/hns3: fix next-to-use overflow when using simple xmit Dongdong Liu
2022-07-27 10:36 ` [PATCH 4/8] net/hns3: optimize SVE xmit performance Dongdong Liu
2022-07-27 10:36 ` [PATCH 5/8] net/hns3: fix segment fault when secondary process access FW Dongdong Liu
2022-07-27 10:36 ` [PATCH 6/8] net/hns3: delete rte unused tag Dongdong Liu
2022-07-27 10:36 ` [PATCH 7/8] net/hns3: fix uncleared hardware MAC statistics Dongdong Liu
2022-07-27 10:36 ` [PATCH 8/8] net/hns3: revert optimize Tx performance Dongdong Liu
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=20220727103616.18596-1-liudongdong3@huawei.com \
--to=liudongdong3@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=stable@dpdk.org \
--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
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).