From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by dpdk.org (Postfix) with ESMTP id E36B54C7F for ; Thu, 1 Mar 2018 10:29:58 +0100 (CET) Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id w219TvUX027820 for ; Thu, 1 Mar 2018 18:29:57 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 48C99EA846B for ; Thu, 1 Mar 2018 18:29:57 +0900 (JST) Received: from jcms-pop21.ecl.ntt.co.jp (jcms-pop21.ecl.ntt.co.jp [129.60.87.134]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 3E734EA8426 for ; Thu, 1 Mar 2018 18:29:57 +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 3A3AE4003B4 for ; Thu, 1 Mar 2018 18:29:57 +0900 (JST) From: Yasufumi Ogawa Message-ID: <8b08be87-6b64-8a4a-53e0-29269011d81c@lab.ntt.co.jp> Date: Thu, 1 Mar 2018 18:28:40 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CC-Mail-RelayStamp: 1 To: spp@dpdk.org X-TM-AS-MML: disable Subject: [spp] Port ID incrementation is changed from DPDK18.02 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: Thu, 01 Mar 2018 09:29:59 -0000 Hi all, Before DPDK 18.02 is fixed, behaviour of rte_eth_dev_get_port_by_name() in lib/librte_ether/rte_ethdev.c is changed by this commit. > 5b7ba3114 ethdev: add port ownership This update is a desirable change to fix a problem for synchronization of port management. However, this function assigns unexpected port_id for SPP. Previsouly, add command of secondary expected to be assigned port_id incrementally and independent among each of other secondary processes. For instance, adding ring 0 for sec 1 and 2 results like as spp > sec 1;status recv:8:{Client ID 1 Idling clinet_id:1 port_id:0,on,PHY,outport:none port_id:1,on,PHY,outport:none port_id:2,on,RING(0),outport:none } spp > sec 2;status recv:9:{Client ID 2 Idling clinet_id:2 port_id:0,on,PHY,outport:none port_id:1,on,PHY,outport:none port_id:2,on,RING(0),outport:none } Both of secondary has port_id:2 for ring 0. However, it is different by using DPDK 18.02. spp > sec 1;status recv:8:{Client ID 1 Idling clinet_id:1 port_id:0,on,PHY,outport:none port_id:1,on,PHY,outport:none port_id:4,on,RING(0),outport:none } spp > sec 2;status recv:9:{Client ID 2 Idling clinet_id:2 port_id:0,on,PHY,outport:none port_id:1,on,PHY,outport:none port_id:5,on,RING(0),outport:none } port_id are different, 4 and 5. It is not a serious problem, but would be annoying for users. I would like to fix it. Luckly, we can patch ports without not port IDs and instead of resource IDs by recent update. So, I will change port assignment to not to use port ID by removing port_id from status. Here is an updated message example. spp > sec 1;status recv:8:{Client ID 1 Idling clinet_id:1 PHY(0),outport:none PHY(1),outport:none RING(0),outport:none } Patching ports with resource IDs is done by spp > patch phy:0 ring:0 Thanks, Yasufumi -- Yasufumi Ogawa NTT Network Service Systems Labs