From: Dongdong Liu <liudongdong3@huawei.com>
To: <dev@dpdk.org>, <ferruh.yigit@amd.com>, <thomas@monjalon.net>,
<andrew.rybchenko@oktetlabs.ru>
Cc: <stable@dpdk.org>, <yisen.zhuang@huawei.com>,
<liudongdong3@huawei.com>, <lihuisong@huawei.com>
Subject: [PATCH 0/6] net/hns3: some code optimization for Rx/Tx function
Date: Sat, 11 Feb 2023 17:18:24 +0800 [thread overview]
Message-ID: <20230211091830.3494-1-liudongdong3@huawei.com> (raw)
This patchset is to do some code optimization for Rx/Tx function.
Huisong Li (6):
net/hns3: fix querying dummy function failed
net/hns3: add debug info for Rx/Tx dummy function
net/hns3: remove debug condition for Tx prepare
net/hns3: separate tx prepare from getting Tx function
net/hns3: remove getting Tx function from head file
net/hns3: extract common functions to set Rx/Tx
drivers/net/hns3/hns3_ethdev.c | 20 ++----
drivers/net/hns3/hns3_ethdev_vf.c | 19 ++----
drivers/net/hns3/hns3_mp.c | 4 +-
drivers/net/hns3/hns3_rxtx.c | 108 ++++++++++++++++++------------
drivers/net/hns3/hns3_rxtx.h | 5 +-
5 files changed, 79 insertions(+), 77 deletions(-)
--
2.22.0
next reply other threads:[~2023-02-11 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 9:18 Dongdong Liu [this message]
2023-02-11 9:18 ` [PATCH 1/6] net/hns3: fix querying dummy function failed Dongdong Liu
2023-02-11 9:18 ` [PATCH 2/6] net/hns3: add debug info for Rx/Tx dummy function Dongdong Liu
2023-02-11 9:18 ` [PATCH 3/6] net/hns3: remove debug condition for Tx prepare Dongdong Liu
2023-02-11 9:18 ` [PATCH 4/6] net/hns3: separate tx prepare from getting Tx function Dongdong Liu
2023-02-11 9:18 ` [PATCH 5/6] net/hns3: remove getting Tx function from head file Dongdong Liu
2023-02-11 9:18 ` [PATCH 6/6] net/hns3: extract common functions to set Rx/Tx Dongdong Liu
2023-02-14 11:54 ` [PATCH 0/6] net/hns3: some code optimization for Rx/Tx function 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=20230211091830.3494-1-liudongdong3@huawei.com \
--to=liudongdong3@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=lihuisong@huawei.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yisen.zhuang@huawei.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).