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/8] refactor logic to support secondary process
Date: Fri, 19 Apr 2024 11:12:18 +0800 [thread overview]
Message-ID: <20240419031226.1191069-1-chaoyong.he@corigine.com> (raw)
Refactor data structure and related logic to make the secondary process
can work as expect.
Chaoyong He (8):
net/nfp: fix resource leak of secondary process
net/nfp: fix configuration BAR problem
net/nfp: adjust the data field of Rx/Tx queue
net/nfp: add the process private structure
net/nfp: move device info data field
net/nfp: unify CPP acquire method
net/nfp: remove ethernet device data field
net/nfp: unify port create and destroy interface
drivers/net/nfp/flower/nfp_flower.c | 125 ++++----
drivers/net/nfp/flower/nfp_flower.h | 11 +-
drivers/net/nfp/flower/nfp_flower_cmsg.c | 5 +-
drivers/net/nfp/flower/nfp_flower_cmsg.h | 3 +-
drivers/net/nfp/flower/nfp_flower_ctrl.c | 8 +-
drivers/net/nfp/flower/nfp_flower_flow.c | 16 +-
.../net/nfp/flower/nfp_flower_representor.c | 151 ++++++----
.../net/nfp/flower/nfp_flower_representor.h | 4 +-
drivers/net/nfp/flower/nfp_flower_service.c | 32 +-
drivers/net/nfp/flower/nfp_flower_service.h | 10 +-
drivers/net/nfp/nfd3/nfp_nfd3_dp.c | 5 +-
drivers/net/nfp/nfdk/nfp_nfdk_dp.c | 5 +-
drivers/net/nfp/nfp_ethdev.c | 274 ++++++++++--------
drivers/net/nfp/nfp_ethdev_vf.c | 18 +-
drivers/net/nfp/nfp_net_common.c | 116 ++++----
drivers/net/nfp/nfp_net_common.h | 30 +-
drivers/net/nfp/nfp_net_flow.c | 20 +-
drivers/net/nfp/nfp_rxtx.c | 9 +-
drivers/net/nfp/nfp_rxtx.h | 69 ++---
drivers/net/nfp/nfpcore/nfp6000_pcie.c | 34 +--
20 files changed, 523 insertions(+), 422 deletions(-)
--
2.39.1
next reply other threads:[~2024-04-19 3:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 3:12 Chaoyong He [this message]
2024-04-19 3:12 ` [PATCH 1/8] net/nfp: fix resource leak of " Chaoyong He
2024-04-19 3:12 ` [PATCH 2/8] net/nfp: fix configuration BAR problem Chaoyong He
2024-04-19 3:12 ` [PATCH 3/8] net/nfp: adjust the data field of Rx/Tx queue Chaoyong He
2024-04-19 3:12 ` [PATCH 4/8] net/nfp: add the process private structure Chaoyong He
2024-04-19 3:12 ` [PATCH 5/8] net/nfp: move device info data field Chaoyong He
2024-04-19 3:12 ` [PATCH 6/8] net/nfp: unify CPP acquire method Chaoyong He
2024-04-19 3:12 ` [PATCH 7/8] net/nfp: remove ethernet device data field Chaoyong He
2024-04-19 3:12 ` [PATCH 8/8] net/nfp: unify port create and destroy interface Chaoyong He
2024-04-19 5:23 ` [PATCH 0/8] refactor logic to support secondary process Chaoyong He
2024-04-19 5:23 ` [PATCH v2 1/8] net/nfp: fix resource leak of " Chaoyong He
2024-04-19 5:23 ` [PATCH v2 2/8] net/nfp: fix configuration BAR problem Chaoyong He
2024-04-19 5:23 ` [PATCH v2 3/8] net/nfp: adjust the data field of Rx/Tx queue Chaoyong He
2024-04-19 5:23 ` [PATCH v2 4/8] net/nfp: add the process private structure Chaoyong He
2024-04-19 5:23 ` [PATCH v2 5/8] net/nfp: move device info data field Chaoyong He
2024-04-19 5:23 ` [PATCH v2 6/8] net/nfp: unify CPP acquire method Chaoyong He
2024-04-19 5:23 ` [PATCH v2 7/8] net/nfp: remove ethernet device data field Chaoyong He
2024-04-19 5:23 ` [PATCH v2 8/8] net/nfp: unify port create and destroy interface Chaoyong He
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=20240419031226.1191069-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).