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/5] Show lcores in status of spp_vf and siblings
Date: Wed,  8 May 2019 10:59:39 +0900	[thread overview]
Message-ID: <1557280784-7620-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)

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

This series of patches is to show lcore IDs in the response of status
command as spp_nfv.

Yasufumi Ogawa (5):
  spp_vf/common: add lcore IDs in status message
  controller: add paring lcore IDs for vf and mirror
  spp-ctl: add master lcore entry for SPP CLI
  spp_pcap: add lcore IDs in status message
  controller: add parsing lcore IDs for spp_pcap

 src/controller/commands/mirror.py | 14 +++++++++++
 src/controller/commands/pcap.py   | 19 +++++++++++++--
 src/controller/commands/vf.py     | 15 ++++++++++--
 src/pcap/command_proc.c           | 11 +++++++++
 src/spp-ctl/spp_webapi.py         |  1 +
 src/vf/common/command_proc.c      | 39 +++++++++++++++++++++++++++++++
 6 files changed, 95 insertions(+), 4 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-05-08  2:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  1:59 ogawa.yasufumi [this message]
2019-05-08  1:59 ` [spp] [PATCH 1/5] spp_vf/common: add lcore IDs in status message ogawa.yasufumi
2019-05-08  1:59 ` [spp] [PATCH 2/5] controller: add paring lcore IDs for vf and mirror ogawa.yasufumi
2019-05-08  1:59 ` [spp] [PATCH 3/5] spp-ctl: add master lcore entry for SPP CLI ogawa.yasufumi
2019-05-08  1:59 ` [spp] [PATCH 4/5] spp_pcap: add lcore IDs in status message ogawa.yasufumi
2019-05-08  1:59 ` [spp] [PATCH 5/5] controller: add parsing lcore IDs for spp_pcap 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=1557280784-7620-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).