From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id E23451B5A9 for ; Thu, 10 Jan 2019 00:35:13 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jan 2019 15:35:11 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,459,1539673200"; d="scan'208";a="116890732" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga003.jf.intel.com with ESMTP; 09 Jan 2019 15:35:12 -0800 Received: from fmsmsx119.amr.corp.intel.com (10.18.124.207) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 9 Jan 2019 15:35:12 -0800 Received: from fmsmsx117.amr.corp.intel.com ([169.254.3.160]) by FMSMSX119.amr.corp.intel.com ([169.254.14.102]) with mapi id 14.03.0415.000; Wed, 9 Jan 2019 15:35:12 -0800 From: "Wiles, Keith" To: Daniel Waddington CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] DPDK on IBM Power9 Thread-Index: AQHUqGpSZYVqVk6qC0OeWdTEZOwlbaWoEU+AgAAISICAAAOdgA== Date: Wed, 9 Jan 2019 23:35:11 +0000 Message-ID: <9C2829AB-34D1-4EB3-BADE-E660349E5E80@intel.com> References: <73991857-48DE-4FE9-9798-045C42AC7B1C@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.9.192] Content-Type: text/plain; charset="us-ascii" Content-ID: <8A62F16F6E822B4391C2B5CF70415918@intel.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] DPDK on IBM Power9 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2019 23:35:14 -0000 > On Jan 9, 2019, at 5:22 PM, Daniel Waddington = wrote: >=20 > This NIC (000:01:00.0) is supported (Intel XL710). I assume that I can us= e VFIO instead of UIO. UIO is really bad from a security perspective. >=20 > I think its the "cannot create new DMA window, error 22" which is the fir= st indicator of the problem. >=20 > Daniel >=20 > -----"Wiles, Keith" wrote: ----- > To: Daniel Waddington > From: "Wiles, Keith" > Date: 01/09/2019 02:52PM > Cc: "dev@dpdk.org" > Subject: Re: [dpdk-dev] DPDK on IBM Power9 >=20 >=20 >> On Jan 9, 2019, at 4:25 PM, Daniel Waddington wrote: >>=20 >> Hi, >> I'm trying to run DPDK 18.11 on IBM Power9. Should it run? (I'n new to= DPDK on Power).=20 >> Thx, >> Daniel >> Below is what I get: >>=20 >> $ sudo ./examples/ethtool/ethtool-app/ppc_64-power8-linuxapp-gcc/app/eth= tool --iova-mode=3Dpa -c7 -w 0000:01:00.0 >> EAL: Detected 128 lcore(s) >> EAL: Detected 2 NUMA nodes >> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket >> EAL: Probing VFIO support... >> EAL: VFIO support initialized >> EAL: PCI device 0000:01:00.0 on NUMA socket 0 >> EAL: probe driver: 8086:1583 net_i40e >> EAL: using IOMMU type 7 (sPAPR) >> EAL: cannot create new DMA window, error 22 (Invalid argument) >> EAL: Could not create new DMA window >> EAL: 0000:01:00.0 DMA remapping failed, error 22 (Invalid argument) >> EAL: Requested device 0000:01:00.0 cannot be used >> Number of NICs: 0 >> EAL: Error - exiting with code: 1 >> Cause: No available NIC ports! >>=20 >=20 > From the message above you need support NIC for DPDK is all or you a NIC = needs to be bound to something like igb_uio for linux. I have never run DPD= K on power before and not sure what is next other then using a supported NI= C. >=20 Yes you should be able to use VFIO. Did you bind the NIC to VFIO ? There should be some docs about how that is done. Beyond this I have not idea? >>=20 >>=20 >=20 > Regards, > Keith >=20 >=20 Regards, Keith