[spp] [RFC] assign global unique port ID
Yasufumi Ogawa
ogawa.yasufumi at lab.ntt.co.jp
Tue Oct 3 08:34:25 CEST 2017
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 at lab.ntt.co.jp
-------------------------------------------------
More information about the spp
mailing list