From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 00/11] Refactor libs for classifier in spp_vf
Date: Mon, 24 Jun 2019 11:24:53 +0900 [thread overview]
Message-ID: <20190624022504.18752-1-yasufum.o@gmail.com> (raw)
From: Yasufumi Ogawa <yasufum.o@gmail.com>
Functions for classifier table are hard to maintain because for long
names of functions and variables, complex dependencies of shared libs
and dedicated functions, or so.
This update is to fix these issues. Some of dependencies are still
remained, but reduced by separating many dedicated functions from shared
libs or adding comments for explaining.
Yasufumi Ogawa (11):
shared/sec: refactor defines of VLAN in spp_vf
shared/sec: rename struct mac_classification
shared/sec: refactor comments in vf_deps.h
shared/sec: rename struct classified_data
shared/sec: revise usage of term component_info
shared/sec: revise members of struct cls_port_info
shared/sec: rename func free_mac_classification
shared/sec: refactor updating classifier info
shared/sec: refactor updating forwarder
shared/sec: refactor getting classifier status
shared/sec: refactor setup cls table stat in JSON
.../secondary/spp_worker_th/cmd_parser.c | 2 +-
.../secondary/spp_worker_th/cmd_runner.c | 37 +-
.../secondary/spp_worker_th/cmd_utils.c | 4 +-
.../secondary/spp_worker_th/cmd_utils.h | 5 +-
src/shared/secondary/spp_worker_th/vf_deps.h | 158 +++-----
src/vf/classifier_mac.c | 382 +++++++++---------
src/vf/classifier_mac.h | 2 +-
src/vf/spp_forward.c | 105 +++--
8 files changed, 330 insertions(+), 365 deletions(-)
--
2.17.1
next reply other threads:[~2019-06-24 2:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 2:24 yasufum.o [this message]
2019-06-24 2:24 ` [spp] [PATCH 01/11] shared/sec: refactor defines of VLAN " yasufum.o
2019-06-24 2:24 ` [spp] [PATCH 02/11] shared/sec: rename struct mac_classification yasufum.o
2019-06-24 2:24 ` [spp] [PATCH 03/11] shared/sec: refactor comments in vf_deps.h yasufum.o
2019-06-24 2:24 ` [spp] [PATCH 04/11] shared/sec: rename struct classified_data yasufum.o
2019-06-24 2:24 ` [spp] [PATCH 05/11] shared/sec: revise usage of term component_info yasufum.o
2019-06-24 2:24 ` [spp] [PATCH 06/11] shared/sec: revise members of struct cls_port_info yasufum.o
2019-06-24 2:25 ` [spp] [PATCH 07/11] shared/sec: rename func free_mac_classification yasufum.o
2019-06-24 2:25 ` [spp] [PATCH 08/11] shared/sec: refactor updating classifier info yasufum.o
2019-06-24 2:25 ` [spp] [PATCH 09/11] shared/sec: refactor updating forwarder yasufum.o
2019-06-24 2:25 ` [spp] [PATCH 10/11] shared/sec: refactor getting classifier status yasufum.o
2019-06-24 2:25 ` [spp] [PATCH 11/11] shared/sec: refactor setup cls table stat in JSON yasufum.o
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=20190624022504.18752-1-yasufum.o@gmail.com \
--to=yasufum.o@gmail.com \
--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).