Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: spp@dpdk.org, ferruh.yigit@intel.com, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/6] Refactor functions for manipulating thread info
Date: Fri, 31 May 2019 12:36:53 +0900	[thread overview]
Message-ID: <1559273819-26243-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)

From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>

This series of update is to refactor functions for manipulating info of
worker thread previously called as component.

Yasufumi Ogawa (6):
  shared/sec: refactor func for deleting comp info
  shared/sec: revise types of spp worker
  shared/sec: rename funcs of flush cmd
  shared/sec: rename file spp_proc to cmd_utils
  shared/sec: refactor name of funcs for exec cmd
  shared/sec: rename struct spp_command

 src/mirror/Makefile                           |   2 +-
 src/mirror/spp_mirror.c                       |  51 +++---
 src/pcap/Makefile                             |   2 +-
 src/pcap/{spp_proc.c => cmd_utils.c}          |   2 +-
 src/pcap/{spp_proc.h => cmd_utils.h}          |   6 +-
 src/pcap/command_dec.h                        |   2 +-
 src/pcap/command_proc.h                       |   2 +-
 src/pcap/spp_pcap.c                           |   2 +-
 src/pcap/spp_pcap.h                           |   2 +-
 .../secondary/spp_worker_th/cmd_parser.c      |  63 +++----
 .../secondary/spp_worker_th/cmd_parser.h      |  12 +-
 .../secondary/spp_worker_th/cmd_runner.c      | 159 +++++++++---------
 .../secondary/spp_worker_th/cmd_runner.h      |  10 +-
 .../spp_worker_th/{spp_proc.c => cmd_utils.c} |  87 +++++-----
 .../spp_worker_th/{spp_proc.h => cmd_utils.h} |  70 ++++----
 .../secondary/spp_worker_th/command_conn.h    |   2 +-
 .../secondary/spp_worker_th/mirror_deps.h     |   2 +-
 .../spp_worker_th/ringlatencystats.c          |   2 +-
 src/shared/secondary/spp_worker_th/spp_port.h |   8 +-
 src/shared/secondary/spp_worker_th/vf_deps.h  |   8 +-
 src/vf/Makefile                               |   2 +-
 src/vf/classifier_mac.c                       |   2 +-
 src/vf/spp_forward.c                          |  23 ++-
 src/vf/spp_vf.c                               |   6 +-
 24 files changed, 263 insertions(+), 264 deletions(-)
 rename src/pcap/{spp_proc.c => cmd_utils.c} (99%)
 rename src/pcap/{spp_proc.h => cmd_utils.h} (99%)
 rename src/shared/secondary/spp_worker_th/{spp_proc.c => cmd_utils.c} (94%)
 rename src/shared/secondary/spp_worker_th/{spp_proc.h => cmd_utils.h} (92%)

-- 
2.17.1


             reply	other threads:[~2019-05-31  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31  3:36 ogawa.yasufumi [this message]
2019-05-31  3:36 ` [spp] [PATCH 1/6] shared/sec: refactor func for deleting comp info ogawa.yasufumi
2019-05-31  3:36 ` [spp] [PATCH 2/6] shared/sec: revise types of spp worker ogawa.yasufumi
2019-05-31  3:36 ` [spp] [PATCH 3/6] shared/sec: rename funcs of flush cmd ogawa.yasufumi
2019-05-31  3:36 ` [spp] [PATCH 4/6] shared/sec: rename file spp_proc to cmd_utils ogawa.yasufumi
2019-05-31  3:36 ` [spp] [PATCH 5/6] shared/sec: refactor name of funcs for exec cmd ogawa.yasufumi
2019-05-31  3:36 ` [spp] [PATCH 6/6] shared/sec: rename struct spp_command 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=1559273819-26243-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).