From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id B8E207CEB for ; Thu, 19 Apr 2018 09:15:26 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Apr 2018 00:15:23 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,468,1517904000"; d="scan'208";a="33722112" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga008.fm.intel.com with ESMTP; 19 Apr 2018 00:15:23 -0700 Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 19 Apr 2018 00:15:23 -0700 Received: from hasmsx105.ger.corp.intel.com (10.184.198.19) by fmsmsx109.amr.corp.intel.com (10.18.116.9) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 19 Apr 2018 00:15:22 -0700 Received: from HASMSX110.ger.corp.intel.com ([169.254.6.227]) by HASMSX105.ger.corp.intel.com ([169.254.1.214]) with mapi id 14.03.0319.002; Thu, 19 Apr 2018 10:15:13 +0300 From: "Rosen, Rami" To: Filip Janiszewski , "users@dpdk.org" Thread-Topic: [dpdk-users] DPDK device name Thread-Index: AQHT16WaACA2SAwaREyr9Nv77qu27aQHq5Kw Date: Thu, 19 Apr 2018 07:15:07 +0000 Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F9531E4503@HASMSX110.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjZiNDQ4YzQtMDUwNC00ZjEyLWJkNGItMWQzZGY3ZWU3YjE3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ5djlOeExkYjJMT3lXS0pKNGVPOEpiWWVmQlpKNFV6dUpDVWJ2S3hYTHhkclZzZStIdFN0UVhBWFp6UWJ3Vm0yIn0= x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [10.255.202.230] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-users] DPDK device name X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 07:15:27 -0000 Hi Flip, I assume that by "port numbers" you mean the PCI bus id (BDF) that is used by DPDK (for bind, for example). You can fetch the bus id for a netdevice named "eth0" by ethtool -i eth0 | grep bus-info bus-info: 0000:01:00.0 If you mean the internal port number (starting from 0 for the first port, a= nd so on) inside DPDK, then there is no=20 mapping between the interface name (as seen by ifconfig) and the internal D= PDK port number. Regards, Rami Rosen -----Original Message----- From: users [mailto:users-bounces@dpdk.org] On Behalf Of Filip Janiszewski Sent: Thursday, April 19, 2018 09:13 To: users@dpdk.org Subject: [dpdk-users] DPDK device name Hi, Is there any mapping between the port names I see while using 'ifconfig' and the port numbers I use normally to handle NIC ports? In other words, is= there a way to identify which ports number corresponds to a given linux in= terface name? Thanks -- BR, Filip +48 666 369 823