From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 0/2] Add lcores in status in spp_nfv
Date: Thu, 31 Jan 2019 12:06:10 +0900 [thread overview]
Message-ID: <1548903972-17562-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 add lcores in status info. Spp_nfv includes
lcores as a list in JSON formatted message.
{"client-id":2,"status":"idling","lcores":[1,2], ...}
SPP CLI shows lcores in the result of status of nfv command.
spp > nfv 2; status
- status: idling
- lcores: [1, 2]
- ports:
- phy:0
...
Yasufumi Ogawa (2):
spp_nfv: add lcores in status info
controller: add lcores in status of spp_nfv
src/controller/commands/nfv.py | 2 ++
src/nfv/commands.h | 2 ++
src/nfv/main.c | 18 ++++++++++++++++--
src/nfv/nfv_status.c | 36 ++++++++++++++++++++++++++++--------
src/nfv/nfv_status.h | 4 ++++
5 files changed, 52 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-31 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 3:06 ogawa.yasufumi [this message]
2019-01-31 3:06 ` [spp] [PATCH 1/2] spp_nfv: add lcores in status info ogawa.yasufumi
2019-01-31 3:06 ` [spp] [PATCH 2/2] controller: add lcores in status of spp_nfv 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=1548903972-17562-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).