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/6] refactor the service module
Date: Wed, 19 Jun 2024 11:06:49 +0800 [thread overview]
Message-ID: <20240619030655.3216268-1-chaoyong.he@corigine.com> (raw)
This patch series refactor the service module, remove some specific
logic and use the service framework logic as much as possible.
Also add a device argument to control the enable of CPP service.
Long Wu (6):
net/nfp: fix check logic for device arguments
net/nfp: remove redundant NFP service code
net/nfp: remove the flower service dead loop
net/nfp: fix disable CPP service
net/nfp: add CPP service enable option
net/nfp: add CPP service abnormal exit logic
doc/guides/nics/nfp.rst | 9 +++
.../net/nfp/flower/nfp_flower_representor.c | 3 -
drivers/net/nfp/flower/nfp_flower_service.c | 29 +++----
drivers/net/nfp/nfp_cpp_bridge.c | 6 ++
drivers/net/nfp/nfp_cpp_bridge.h | 1 +
drivers/net/nfp/nfp_ethdev.c | 81 ++++++++++++++-----
drivers/net/nfp/nfp_net_common.h | 3 +
drivers/net/nfp/nfp_service.c | 76 +++--------------
drivers/net/nfp/nfp_service.h | 1 -
9 files changed, 101 insertions(+), 108 deletions(-)
--
2.39.1
next reply other threads:[~2024-06-19 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 3:06 Chaoyong He [this message]
2024-06-19 3:06 ` [PATCH 1/6] net/nfp: fix check logic for device arguments Chaoyong He
2024-06-19 3:06 ` [PATCH 2/6] net/nfp: remove redundant NFP service code Chaoyong He
2024-06-19 3:06 ` [PATCH 3/6] net/nfp: remove the flower service dead loop Chaoyong He
2024-06-19 3:06 ` [PATCH 4/6] net/nfp: fix disable CPP service Chaoyong He
2024-06-19 3:06 ` [PATCH 5/6] net/nfp: add CPP service enable option Chaoyong He
2024-06-19 3:06 ` [PATCH 6/6] net/nfp: add CPP service abnormal exit logic Chaoyong He
2024-07-06 18:51 ` [PATCH 0/6] refactor the service module 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=20240619030655.3216268-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).