From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/5] Add support of report packet type
Date: Mon, 22 May 2023 16:04:55 +0800 [thread overview]
Message-ID: <20230522080500.2014001-1-chaoyong.he@corigine.com> (raw)
This patch series add the support of report packet type function for
NFP PMD:
- Add a new contributor entry
- Rename one data field of RX descriptor
- Refactor the logic of NFP reconfig
- Add the logic of report packet type
Qin Ke (5):
mailmap: update contributor entry
net/nfp: rename field and add comment for Rx descriptor
net/nfp: standardize the logic for nfp reconfig function
net/nfp: remove logic of reporting packet type by hash type
net/nfp: report packet type by Rx descriptor
.mailmap | 1 +
drivers/net/nfp/flower/nfp_flower.c | 2 +-
drivers/net/nfp/nfp_common.c | 72 ++++++++++---
drivers/net/nfp/nfp_common.h | 1 +
drivers/net/nfp/nfp_ctrl.h | 16 ++-
drivers/net/nfp/nfp_ethdev.c | 12 ++-
drivers/net/nfp/nfp_rxtx.c | 162 +++++++++++++++++++++++-----
drivers/net/nfp/nfp_rxtx.h | 107 +++++++++++++++---
8 files changed, 315 insertions(+), 58 deletions(-)
--
2.39.1
next reply other threads:[~2023-05-22 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 8:04 Chaoyong He [this message]
2023-05-22 8:04 ` [PATCH 1/5] mailmap: update contributor entry Chaoyong He
2023-05-22 8:04 ` [PATCH 2/5] net/nfp: rename field and add comment for Rx descriptor Chaoyong He
2023-05-22 8:04 ` [PATCH 3/5] net/nfp: standardize the logic for nfp reconfig function Chaoyong He
2023-05-22 8:04 ` [PATCH 4/5] net/nfp: remove logic of reporting packet type by hash type Chaoyong He
2023-05-22 8:05 ` [PATCH 5/5] net/nfp: report packet type by Rx descriptor Chaoyong He
2023-06-02 16:26 ` [PATCH 0/5] Add support of report packet type 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=20230522080500.2014001-1-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).