From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by dpdk.org (Postfix) with ESMTP id ED34E1B2E1 for ; Tue, 3 Oct 2017 08:34:57 +0200 (CEST) Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id v936YuJE030711; Tue, 3 Oct 2017 15:34:56 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 36FE45F63F; Tue, 3 Oct 2017 15:34:56 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 2A8FC5F593; Tue, 3 Oct 2017 15:34:56 +0900 (JST) Received: from [IPv6:::1] (watercress.nslab.ecl.ntt.co.jp [129.60.13.73]) by jcms-pop21.ecl.ntt.co.jp (Postfix) with ESMTPSA id 241D6400C30; Tue, 3 Oct 2017 15:34:56 +0900 (JST) From: Yasufumi Ogawa Message-ID: <093f4d79-1238-3be8-f242-062bca27a933@lab.ntt.co.jp> Date: Tue, 3 Oct 2017 15:34:25 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit To: spp@dpdk.org Cc: srv-apl-arch@lab.ntt.co.jp, "Choi, Sy Jong" , gerald.rogers@intel.com X-TM-AS-MML: disable Subject: [spp] [RFC] assign global unique port ID X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Oct 2017 06:34:58 -0000 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 -------------------------------------------------