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/4] Port management with resource UID
Date: Tue, 9 Oct 2018 19:48:43 +0900 [thread overview]
Message-ID: <20181009104847.42502-1-ogawa.yasufumi@lab.ntt.co.jp> (raw)
From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
Resource UID (called resource ID previously) consists of port type and
port ID was introduced to specify a port. For example, users can patch
ports as following.
spp > sec 1; patch phy:0 ring:0 # instead of 'patch 0 1'
However, add and del commands are still remained using old style of
resource UID.
spp > sec 1; add ring 0 # should be updated to 'add ring:0'
This series of patches is to update the usage of resource UID.
* Add a common function parse_resource_uid() to extract port type and ID
from resource UID.
* Update spp_nfv and spp_vm to use parse_resource_uid().
* Update add and del command in SPP controller to use the latest style
of resource UID.
Yasufumi Ogawa (4):
shared: add parsing resource UID
spp_nfv: change to use parse_resource_uid
spp_vm: change to use parse_resource_uid
controller: unify accepting resource UID format
src/controller/shell.py | 16 ++++--
src/nfv/nfv.c | 143 ++++++++++++++----------------------------------
src/shared/common.c | 24 ++++++++
src/shared/common.h | 1 +
src/vm/main.c | 103 ++++++++++------------------------
5 files changed, 104 insertions(+), 183 deletions(-)
--
2.7.4
next reply other threads:[~2018-10-09 10:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 10:48 ogawa.yasufumi [this message]
2018-10-09 10:48 ` [spp] [PATCH 1/4] shared: add parsing " ogawa.yasufumi
2018-10-09 10:48 ` [spp] [PATCH 2/4] spp_nfv: change to use parse_resource_uid ogawa.yasufumi
2018-10-09 10:48 ` [spp] [PATCH 3/4] spp_vm: " ogawa.yasufumi
2018-10-09 10:48 ` [spp] [PATCH 4/4] controller: unify accepting resource UID format 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=20181009104847.42502-1-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).