From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 00/11] Refactor functions for handling commands
Date: Fri, 31 May 2019 12:35:54 +0900 [thread overview]
Message-ID: <1559273765-26130-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Some of function in SPP workers such as parsing command or checking
params for are named or have comments inappropriately. This series of
update is to refactor this issues.
Yasufumi Ogawa (11):
shared/sec: rename functions of sppwk_cmd_runner
shared/sec: revise enum for cmd response
shared/sec: refactor passing err in cmd_runner
shared/sec: rename struct for command response
shared/sec: refactor funcs for managing port info
shared/sec: rename util functions in cmd_runner
shared/sec: rename func for getting component ID
shared/sec: refactor func for updating cls table
shared/sec: rename func for executing command
shared/sec: add helpers for logging cmd parser
shared/sec: rename func for updating port
src/mirror/spp_mirror.c | 4 +-
.../secondary/spp_worker_th/cmd_parser.c | 52 ++-
.../secondary/spp_worker_th/cmd_parser.h | 4 +
.../secondary/spp_worker_th/cmd_runner.c | 408 ++++++++----------
.../secondary/spp_worker_th/cmd_runner.h | 32 +-
src/shared/secondary/spp_worker_th/spp_proc.c | 76 ++--
src/shared/secondary/spp_worker_th/spp_proc.h | 53 +--
src/vf/spp_vf.c | 4 +-
8 files changed, 319 insertions(+), 314 deletions(-)
--
2.17.1
next reply other threads:[~2019-05-31 3:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 3:35 ogawa.yasufumi [this message]
2019-05-31 3:35 ` [spp] [PATCH 01/11] shared/sec: rename functions of sppwk_cmd_runner ogawa.yasufumi
2019-05-31 3:35 ` [spp] [PATCH 02/11] shared/sec: revise enum for cmd response ogawa.yasufumi
2019-05-31 3:35 ` [spp] [PATCH 03/11] shared/sec: refactor passing err in cmd_runner ogawa.yasufumi
2019-05-31 3:35 ` [spp] [PATCH 04/11] shared/sec: rename struct for command response ogawa.yasufumi
2019-05-31 3:35 ` [spp] [PATCH 05/11] shared/sec: refactor funcs for managing port info ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 06/11] shared/sec: rename util functions in cmd_runner ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 07/11] shared/sec: rename func for getting component ID ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 08/11] shared/sec: refactor func for updating cls table ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 09/11] shared/sec: rename func for executing command ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 10/11] shared/sec: add helpers for logging cmd parser ogawa.yasufumi
2019-05-31 3:36 ` [spp] [PATCH 11/11] shared/sec: rename func for updating port ogawa.yasufumi
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=1559273765-26130-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=ferruh.yigit@intel.com \
--cc=spp@dpdk.org \
/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).