Soft Patch Panel
 help / color / mirror / Atom feed
From: ogawa.yasufumi@lab.ntt.co.jp
To: ferruh.yigit@intel.com, spp@dpdk.org, ogawa.yasufumi@lab.ntt.co.jp
Subject: [spp] [PATCH 2/2] controller: add lcores in status of spp_nfv
Date: Thu, 31 Jan 2019 12:06:12 +0900	[thread overview]
Message-ID: <1548903972-17562-3-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)
In-Reply-To: <1548903972-17562-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp>

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

This update is to show lcores in status of nfv command. Here is an
example.

  spp > nfv 1; status
  - status: idling
  - lcores: [1, 2]
  - ports:
    - phy:0
    ...

Signed-off-by: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
---
 src/controller/commands/nfv.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/controller/commands/nfv.py b/src/controller/commands/nfv.py
index e6f95d0..2613bc2 100644
--- a/src/controller/commands/nfv.py
+++ b/src/controller/commands/nfv.py
@@ -67,6 +67,7 @@ class SppNfv(object):
 
           spp > nfv 1;status
           - status: idling
+          - lcores: [1, 2]
           - ports:
             - phy:0 -> ring:0
             - phy:1
@@ -74,6 +75,7 @@ class SppNfv(object):
 
         nfv_attr = json_obj
         print('- status: %s' % nfv_attr['status'])
+        print('- lcores: %s' % nfv_attr['lcores'])
         print('- ports:')
         for port in nfv_attr['ports']:
             dst = None
-- 
2.7.4

      parent 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 [spp] [PATCH 0/2] Add lcores in status in spp_nfv ogawa.yasufumi
2019-01-31  3:06 ` [spp] [PATCH 1/2] spp_nfv: add lcores in status info ogawa.yasufumi
2019-01-31  3:06 ` ogawa.yasufumi [this message]

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-3-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).