Soft Patch Panel
 help / color / mirror / Atom feed
From: yasufum.o@gmail.com
To: spp@dpdk.org, ferruh.yigit@intel.com, yasufum.o@gmail.com
Subject: [spp] [PATCH 0/9] Refactor ringlatencystats
Date: Thu, 12 Sep 2019 19:48:15 +0900	[thread overview]
Message-ID: <20190912104824.21519-1-yasufum.o@gmail.com> (raw)

From: Yasufumi Ogawa <yasufum.o@gmail.com>

Spp_vf and spp_mirror support a feature for measuring latency of ring
PMD intended to be used by developers to roughly evaluate performance.
It is implemented as a set of utility functions. Howver, usage is not
intuitive for users because the name of functions are redundant,
lackness of comments, or log messages are not clear.

This series of update is to refactor the feature.

Yasufumi Ogawa (9):
  shared: rename file ringlatencystats to be short
  shared: rename func for calc latency of ring
  shared: rename struct for ring latency stats
  shared: rename func for init latency stats
  shared: renaem util funcs of ring latency
  spp_vf: revise util func for status command
  spp_mirror: revise util func for status command
  spp_pcap: revise util func for status command
  shared: add TODO to fix bug in latency stats

 src/mirror/Makefile                           |  6 +-
 src/mirror/mir_cmd_runner.c                   | 23 +++---
 src/mirror/spp_mirror.c                       |  6 +-
 src/pcap/Makefile                             |  2 +-
 src/pcap/cmd_runner.c                         | 12 +--
 src/pcap/spp_pcap.c                           |  2 +-
 .../{ringlatencystats.c => latency_stats.c}   | 68 ++++++++--------
 .../{ringlatencystats.h => latency_stats.h}   | 77 +++++++++----------
 .../secondary/spp_worker_th/port_capability.c |  7 +-
 src/vf/Makefile                               |  6 +-
 src/vf/classifier.c                           |  2 +-
 src/vf/forwarder.c                            |  2 +-
 src/vf/spp_vf.c                               |  6 +-
 src/vf/vf_cmd_runner.c                        | 23 +++---
 14 files changed, 113 insertions(+), 129 deletions(-)
 rename src/shared/secondary/spp_worker_th/{ringlatencystats.c => latency_stats.c} (73%)
 rename src/shared/secondary/spp_worker_th/{ringlatencystats.h => latency_stats.h} (67%)

-- 
2.17.1


             reply	other threads:[~2019-09-12 10:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-12 10:48 yasufum.o [this message]
2019-09-12 10:48 ` [spp] [PATCH 1/9] shared: rename file ringlatencystats to be short yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 2/9] shared: rename func for calc latency of ring yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 3/9] shared: rename struct for ring latency stats yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 4/9] shared: rename func for init " yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 5/9] shared: renaem util funcs of ring latency yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 6/9] spp_vf: revise util func for status command yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 7/9] spp_mirror: " yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 8/9] spp_pcap: " yasufum.o
2019-09-12 10:48 ` [spp] [PATCH 9/9] shared: add TODO to fix bug in latency stats 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=20190912104824.21519-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).