From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH 0/4] Support new card using NFP 3800 chip
Date: Tue, 3 Sep 2024 09:41:41 +0800 [thread overview]
Message-ID: <20240903014145.2635710-1-chaoyong.he@corigine.com> (raw)
This patch series add support of a new card which using the NFP 3800 chip.
Because it has different configure BAR size and flow steering rules
limit, we also do some refactor to the related logic.
Chaoyong He (4):
net/nfp: add a new flag to indicate PF
net/nfp: refactor the firmware version logic
net/nfp: support different configuration BAR size
net/nfp: support different flow steering rules limit
drivers/common/nfp/nfp_common_ctrl.h | 13 +++-
drivers/net/nfp/flower/nfp_flower.c | 34 +++++----
drivers/net/nfp/flower/nfp_flower_ctrl.c | 8 +--
drivers/net/nfp/flower/nfp_flower_ctrl.h | 2 +-
drivers/net/nfp/nfd3/nfp_nfd3_dp.c | 2 +-
drivers/net/nfp/nfdk/nfp_nfdk_dp.c | 2 +-
drivers/net/nfp/nfp_ethdev.c | 55 +++++++++------
drivers/net/nfp/nfp_ethdev_vf.c | 33 +++++++--
drivers/net/nfp/nfp_net_common.c | 87 +++++++++++++++++-------
drivers/net/nfp/nfp_net_common.h | 25 ++++---
drivers/net/nfp/nfp_net_ctrl.c | 4 +-
drivers/net/nfp/nfp_net_flow.c | 51 ++++++++++++--
drivers/net/nfp/nfp_net_meta.c | 5 +-
drivers/net/nfp/nfp_net_meta.h | 5 +-
drivers/net/nfp/nfp_rxtx.c | 10 +--
15 files changed, 231 insertions(+), 105 deletions(-)
--
2.39.1
next reply other threads:[~2024-09-03 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 1:41 Chaoyong He [this message]
2024-09-03 1:41 ` [PATCH 1/4] net/nfp: add a new flag to indicate PF Chaoyong He
2024-09-03 1:41 ` [PATCH 2/4] net/nfp: refactor the firmware version logic Chaoyong He
2024-09-03 1:41 ` [PATCH 3/4] net/nfp: support different configuration BAR size Chaoyong He
2024-09-03 1:41 ` [PATCH 4/4] net/nfp: support different flow steering rules limit Chaoyong He
2024-10-04 4:26 ` [PATCH 0/4] Support new card using NFP 3800 chip 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=20240903014145.2635710-1-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--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).