Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-02 Thread Burakov, Anatoly
On 01-Aug-19 2:01 PM, David Marchand wrote: Hello Anatoly, On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura wrote: Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) because of the inconsistency of user's request a

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-02 Thread David Marchand
On Fri, Aug 2, 2019 at 10:09 AM Takeshi T Yoshimura wrote: > > -David Marchand wrote: - > > >To: Takeshi T Yoshimura > >From: David Marchand > >Date: 08/01/2019 06:47PM > >Cc: dev , David Christensen > >Subject: [EXTERNAL] Re: [dpdk-dev] [P

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-02 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi T Yoshimura >From: David Marchand >Date: 08/01/2019 06:47PM >Cc: dev , David Christensen >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >On Thu, Aug 1, 2019 at 10:46 AM Takeshi T Yoshimura &

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-01 Thread David Marchand
Hello Anatoly, On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura wrote: > > Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI > drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) > because of the inconsistency of user's request and the result of > device capability for

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-01 Thread David Marchand
On Thu, Aug 1, 2019 at 10:46 AM Takeshi T Yoshimura wrote: > > > - Are the (below) devices bound to vfio-pci or any other kmod at this point > > of the init? > > Yes, vfio-pci is bound to 0030:01:00.0 in the log. > > > - Is the spdk_nvme driver loaded at this point? > > No, spdk just attempts to

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-01 Thread Takeshi T Yoshimura
> - Are the (below) devices bound to vfio-pci or any other kmod at this point > of the init? Yes, vfio-pci is bound to 0030:01:00.0 in the log. > - Is the spdk_nvme driver loaded at this point? No, spdk just attempts to initialize dpdk at this point. After the initialization finishes, spdk prob

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-08-01 Thread David Marchand
On Thu, Aug 1, 2019 at 7:25 AM Takeshi T Yoshimura wrote: > Okay. I should have set the --log-level=lib.*:debug. Here is the log. > > Starting SPDK v19.10-pre / DPDK 19.08.0-rc3 initialization... > [ DPDK EAL parameters: identify --no-shconf -c 0x1 -n 1 -m 0 > --log-level=lib.eal:6 --log-level=li

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi T Yoshimura >From: David Marchand >Date: 08/01/2019 02:01PM >Cc: dev , David Christensen >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >Hello, > >On Thu, Aug 1, 2019 at 6:10 AM Takeshi

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
On Wed, Jul 31, 2019 at 11:20 PM David Christensen wrote: > > >> Here's the output from my Power 9 system running 19.08-RC2 (I'm not > >> using VFIO since I have an MLX5 adapter). > >> > >> sudo -E LD_LIBRARY_PATH=/home/davec/src/dpdk/build/lib > >> /home/davec/src/dpdk/build/app/testpmd --log-lev

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
Hello, On Thu, Aug 1, 2019 at 6:10 AM Takeshi T Yoshimura wrote: > Here's the full debug log I got. I ran upstream SPDK on NVMe on IBM Power9 > AC922. > The operating system is Ubuntu 18.04 and Linux 4.17. > > Starting SPDK v19.07-pre / DPDK 19.08.0-rc3 initialization... > [ DPDK EAL parameters:

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi T Yoshimura >From: David Marchand >Date: 08/01/2019 04:45AM >Cc: dev , David Christensen >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >On Wed, Jul 31, 2019 at 12:44 PM Takeshi T Yoshimura &

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi T Yoshimura >From: David Marchand >Date: 08/01/2019 04:45AM >Cc: dev , David Christensen >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >On Wed, Jul 31, 2019 at 12:44 PM Takeshi T Yoshimura &

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Christensen
Here's the output from my Power 9 system running 19.08-RC2 (I'm not using VFIO since I have an MLX5 adapter). sudo -E LD_LIBRARY_PATH=/home/davec/src/dpdk/build/lib /home/davec/src/dpdk/build/app/testpmd --log-level lib.\*:debug -w :01:00.0 -w :01:00.1 -l 4,8-79 -n 4 -- --rxq=32 --rxd=10

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
On Wed, Jul 31, 2019 at 12:44 PM Takeshi T Yoshimura wrote: > > -David Marchand wrote: - > > >To: Takeshi Yoshimura > >From: David Marchand > >Date: 07/31/2019 06:29PM > >Cc: dev > >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOV

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
On Wed, Jul 31, 2019 at 9:23 PM David Christensen wrote: > > On 7/31/19 3:58 AM, David Marchand wrote: > > --log-level lib.*:debug > > Here's the output from my Power 9 system running 19.08-RC2 (I'm not > using VFIO since I have an MLX5 adapter). > > sudo -E LD_LIBRARY_PATH=/home/davec/src/dpdk/bu

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Christensen
On 7/31/19 3:58 AM, David Marchand wrote: --log-level lib.*:debug Here's the output from my Power 9 system running 19.08-RC2 (I'm not using VFIO since I have an MLX5 adapter). sudo -E LD_LIBRARY_PATH=/home/davec/src/dpdk/build/lib /home/davec/src/dpdk/build/app/testpmd --log-level lib.\*:de

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
On Wed, Jul 31, 2019 at 12:44 PM Takeshi T Yoshimura wrote: > Ah, I overlooked your first question. The "ppc driver" is in > drivers/bus/pci/linux/pci.c. In pci.c, pci_one_device_iommu_support_va() > always returns false in ppc. so, the driver does not allow VA mode in ppc. > > This return value i

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi Yoshimura >From: David Marchand >Date: 07/31/2019 06:29PM >Cc: dev >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura >wrote: >> >&

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Takeshi T Yoshimura
-David Marchand wrote: - >To: Takeshi Yoshimura >From: David Marchand >Date: 07/31/2019 06:29PM >Cc: dev >Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in >ppc > >On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura >wrote: >> >&

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread David Marchand
On Wed, Jul 31, 2019 at 5:36 AM Takeshi Yoshimura wrote: > > Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI > drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) > because of the inconsistency of user's request and the result of > device capability for IOVA mode. I up

Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-31 Thread Burakov, Anatoly
On 31-Jul-19 4:35 AM, Takeshi Yoshimura wrote: Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) because of the inconsistency of user's request and the result of device capability for IOVA mode. I updated the code to f

[dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc

2019-07-30 Thread Takeshi Yoshimura
Commit b76fafb174d2 ("eal: fix IOVA mode selection as VA for PCI drivers") breaks ppc apps with no IOVA configs (or RTE_IOVA_DC) because of the inconsistency of user's request and the result of device capability for IOVA mode. I updated the code to force IOVA as PA in ppc as before because current