From: Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>
To: spp@dpdk.org
Cc: srv-apl-arch@lab.ntt.co.jp, "Choi,
Sy Jong" <sy.jong.choi@intel.com>,
gerald.rogers@intel.com
Subject: [spp] [RFC] assign global unique port ID
Date: Tue, 3 Oct 2017 15:34:25 +0900 [thread overview]
Message-ID: <093f4d79-1238-3be8-f242-062bca27a933@lab.ntt.co.jp> (raw)
Hi, Gerald, Sy Jong,
In spp, port ID is assigned as a number incrementally and the number of
ID can be different from each sec processes. For instance, ring 0 is
added to sec 1 at first while it is added to sec 2 after ring 1, ring 0
is referred as port 2 from sec 1 and port 3 from sec 2.
spp > sec 1;status
...
port id: 0,on,PHY,outport: -99
port id: 1,on,PHY,outport: -99
port id: 2,on,RING(0),outport: -99 # ring 0 is referred as port 2
spp > sec 2;status
...
port id: 0,on,PHY,outport: -99
port id: 1,on,PHY,outport: -99
port id: 2,on,RING(1),outport: -99
port id: 3,on,RING(0),outport: -99 # ring 0 is referred as port 3
User always has to check the status any time patching to avoid mistake.
However, it must be annoying and an error is possibly happened.
I propose to assign global unique ID for port. In this update, port ID
is referred as a combination of PMD type and its ID, not a number. For
instance,
(Before) spp> patch 0 2
(After) spp> patch phy:0 ring:0 # means to patch from phy 0 to ring 0
If you agree, I would like to send patches for update.
Thanks,
Yasufumi
--
-------------------------------------------------
Yasufumi Ogawa
NTT Network Service Systems Labs
tel: 0422(59)5776 fax: 0422(59)5653
email: ogawa.yasufumi@lab.ntt.co.jp
-------------------------------------------------
next reply other threads:[~2017-10-03 6:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 6:34 Yasufumi Ogawa [this message]
2018-01-29 12:44 ` Yasufumi Ogawa
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=093f4d79-1238-3be8-f242-062bca27a933@lab.ntt.co.jp \
--to=ogawa.yasufumi@lab.ntt.co.jp \
--cc=gerald.rogers@intel.com \
--cc=spp@dpdk.org \
--cc=srv-apl-arch@lab.ntt.co.jp \
--cc=sy.jong.choi@intel.com \
/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).