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 0/3] Add getting lcores feature
Date: Thu, 31 Jan 2019 12:05:03 +0900	[thread overview]
Message-ID: <1548903906-17403-1-git-send-email-ogawa.yasufumi@lab.ntt.co.jp> (raw)

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

How to assign cores depends on a decision of user, but made a mistake
sometimes because it could be complex if there are many cores and
several DPDK processes running on. User should be able to know while
making a decision of core assiginment.

This series of patches is to add a feature to inspect core usage of
spp_priamry. You can get the core usage from spp-ctl or SPP CLI as a
part of status info.

  spp > pri; status
  - lcores:
    - [0, 1]
  - physical ports:
      ID          rx          tx     tx_drop  mac_addr
       0           0           0           0  56:48:4f:53:54:00

It is also available to get CPU layout from spp-ctl, logical cores and
physical cores on each of sockets. It cannot be referred from SPP CLI
currently. Here is an example of getting CPU layout of single socket.
`jq' is a command to show JSON data in well formatted.

  $ curl http://192.168.1.100:7777/v1/cpus | jq
  [
    {
      "cores": [
        {
          "cpus": [
            1
          ],
          "core_id": 1
        },
        ...
      ],
      "socket_id": 0
    }
  ]

The rest of SPP processes are supported in a future update.


Yasufumi Ogawa (3):
  spp_primary: add lcores in status info
  controller: add lcores in status command of pri
  spp-ctl: add API for getting CPU layout

 src/controller/commands/pri.py | 33 ++++++++++++++++++++-------------
 src/primary/init.h             |  2 ++
 src/primary/main.c             | 34 +++++++++++++++++++++++++++-------
 src/spp-ctl/spp_ctl.py         | 25 +++++++++++++++++++++++++
 src/spp-ctl/spp_webapi.py      |  4 ++++
 5 files changed, 78 insertions(+), 20 deletions(-)

-- 
2.7.4

             reply	other threads:[~2019-01-31  3:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31  3:05 ogawa.yasufumi [this message]
2019-01-31  3:05 ` [spp] [PATCH 1/3] spp_primary: add lcores in status info ogawa.yasufumi
2019-01-31  3:05 ` [spp] [PATCH 2/3] controller: add lcores in status command of pri ogawa.yasufumi
2019-01-31  3:05 ` [spp] [PATCH 3/3] spp-ctl: add API for getting CPU layout 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=1548903906-17403-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).