DPDK patches and discussions
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Olga Shern <olgas@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "JPF@zurich.ibm.com" <JPF@zurich.ibm.com>,
	Gowrishankar Muthukrishnan <gowrishankar.m@in.ibm.com>
Subject: Re: [dpdk-dev] [PATCH dpdk 0/5] ppc64/spapr: Attempt to use on POWER8
Date: Sun, 23 Apr 2017 23:35:17 +1000	[thread overview]
Message-ID: <20a6a7f9-ed94-0e0f-aa65-75270cbc0b2b@ozlabs.ru> (raw)
In-Reply-To: <DB6PR0501MB27571CB1BB10E778DE0AB3B8D31D0@DB6PR0501MB2757.eurprd05.prod.outlook.com>

On 23/04/17 07:11, Olga Shern wrote:
> Alexey, 
> 
> Mellanox support DPDK only on Ethernet, no IB.
> And yes, you need to install Mellanox drivers , OFED, to support it.


ibv_get_device_list(&i) returns no devices, the name suggests "ib" ==
infiniband but it may be just naming issue :)


> What NIC do you have? 

Mellanox Technologies MT27520 Family [ConnectX-3 Pro]
Mellanox Technologies MT27700 Family [ConnectX-4]



> 
> Best Regards,
> Olga
> 
> ________________________________________________________________
> Olga Shern 
> SW Director DPDK 
> Mellanox Technologies, Raanana Israel
> 
> 
> 
> 
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alexey
>> Kardashevskiy
>> Sent: Thursday, April 20, 2017 10:24 AM
>> To: dev@dpdk.org
>> Cc: Alexey Kardashevskiy <aik@ozlabs.ru>; JPF@zurich.ibm.com;
>> Gowrishankar Muthukrishnan <gowrishankar.m@in.ibm.com>
>> Subject: [dpdk-dev] [PATCH dpdk 0/5] ppc64/spapr: Attempt to use on
>> POWER8
>>
>> Hi!
>>
>> This is my first attempt to use DPDK on POWER8 machine and yet
>> unsuccessful as it turned out DPDK only supports IB-Mellanox (I only got
>> ethernet-Mellanox, and requires OFED), rmmod on Intel 40Gb module
>> produces PCI errors (unrelated to DPDK) and Broadcom bnx2x has few issues
>> (below) and still crashes as I suspect I got DMA mapping wrong, here is a
>> backtrace:
>>
>> Configuring Port 0 (socket 0)
>> PMD: bnx2x_issue_dmae_with_comp(): DMAE timeout!
>> PANIC in bnx2x_write_dmae():
>> DMAE failed (-1)22: [/lib/powerpc64le-linux-
>> gnu/libc.so.6(__libc_start_main+0xb8) [0x3fffb7c23298]]
>> 21: [/lib/powerpc64le-linux-gnu/libc.so.6(+0x2309c) [0x3fffb7c2309c]]
>> 20: [/home/aik/pbuild/dpdk_build/app/testpmd(main+0x228) [0x100255d0]]
>> 19: [/home/aik/pbuild/dpdk_build/app/testpmd(start_port+0x5dc)
>> [0x1002341c]]
>> 18: [/home/aik/pbuild/dpdk_build/app/testpmd(rte_eth_dev_start+0xc4)
>> [0x1008b3c0]]
>> 17: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x10117550]]
>> 16: [/home/aik/pbuild/dpdk_build/app/testpmd(bnx2x_init+0x204)
>> [0x100f7210]]
>> 15: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100f6888]]
>> 14: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100ee7f4]]
>> 13:
>> [/home/aik/pbuild/dpdk_build/app/testpmd(ecore_func_state_change+0x
>> 250) [0x10127794]]
>> 12: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x1012734c]]
>> 11: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x10126830]]
>> 10: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x10126618]]
>> 9: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x10100a98]]
>> 8: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100ffe00]]
>> 7: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100de614]]
>> 6: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100de4cc]]
>> 5: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x101063c0]]
>> 4: [/home/aik/pbuild/dpdk_build/app/testpmd() [0x100e1f6c]]
>> 3: [/home/aik/pbuild/dpdk_build/app/testpmd(bnx2x_write_dmae+0x11c)
>> [0x100e1e40]]
>> 2: [/home/aik/pbuild/dpdk_build/app/testpmd(__rte_panic+0x8c)
>> [0x100b3e58]]
>> 1: [/home/aik/pbuild/dpdk_build/app/testpmd(rte_dump_stack+0x40)
>> [0x100b3cc4]]
>>
>> Thread 1 "testpmd" received signal SIGABRT, Aborted.
>> 0x00003fffb7c3edb0 in __GI_raise (sig=<optimised out>) at
>> ../sysdeps/unix/sysv/linux/raise.c:54
>> 54      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
>>
>> Still, some fixes are quite obvious and straigtforward.
>>
>> This is based on sha1
>> 2fc8e0bf0 Olivier Matz "log: fix dump of registered logs when disabled".
>>
>> Please comment. Thanks.
>>
>>
>>
>> Alexey Kardashevskiy (5):
>>   vfio/ppc64/spapr: Use correct structures for add/remove windows
>>   pci: Initialize common rte driver pointer
>>   RFC: bnx2x: Update firmware versions
>>   vfio: Do try setting IOMMU type if already set
>>   RFC: vfio/ppc64/spapr: Use correct bus addresses for DMA map
>>
>>  lib/librte_eal/linuxapp/eal/eal_vfio.h |  8 +++++
>>  drivers/net/bnx2x/bnx2x.c              |  4 +--
>>  lib/librte_eal/common/eal_common_pci.c |  1 +
>> lib/librte_eal/linuxapp/eal/eal_vfio.c | 62 +++++++++++++++++++------------
>> ---
>>  4 files changed, 46 insertions(+), 29 deletions(-)
>>
>> --
>> 2.11.0
> 


-- 
Alexey

      reply	other threads:[~2017-04-23 13:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20  7:23 Alexey Kardashevskiy
2017-04-20  7:23 ` [dpdk-dev] [PATCH dpdk 1/5] vfio/ppc64/spapr: Use correct structures for add/remove windows Alexey Kardashevskiy
2017-04-20  7:23 ` [dpdk-dev] [PATCH dpdk 2/5] pci: Initialize common rte driver pointer Alexey Kardashevskiy
2017-04-24  9:28   ` Burakov, Anatoly
2017-04-20  7:24 ` [dpdk-dev] [PATCH dpdk 3/5] RFC: bnx2x: Update firmware versions Alexey Kardashevskiy
2017-04-20  7:24 ` [dpdk-dev] [PATCH dpdk 4/5] vfio: Do try setting IOMMU type if already set Alexey Kardashevskiy
2017-04-20 19:31   ` gowrishankar muthukrishnan
2017-04-21  8:54   ` Andrew Rybchenko
2017-04-26  7:50     ` Alexey Kardashevskiy
2017-04-26  8:27       ` Burakov, Anatoly
2017-04-26  8:45         ` Alejandro Lucero
2017-04-26  8:58           ` Burakov, Anatoly
2017-04-26 10:24             ` Alejandro Lucero
2017-04-20  7:24 ` [dpdk-dev] [PATCH dpdk 5/5] RFC: vfio/ppc64/spapr: Use correct bus addresses for DMA map Alexey Kardashevskiy
2017-04-20  9:04   ` Jonas Pfefferle1
2017-04-20 13:25     ` Alexey Kardashevskiy
2017-04-20 14:22       ` Alexey Kardashevskiy
2017-04-20 15:15         ` Jonas Pfefferle1
2017-04-20 22:01           ` Alexey Kardashevskiy
2017-04-20 19:16         ` gowrishankar muthukrishnan
2017-04-21  3:42           ` Alexey Kardashevskiy
2017-04-21  8:43             ` Alexey Kardashevskiy
     [not found]               ` <OF6F33ED54.7950E1EF-ONC1258109.003295E3-C1258109.00333E2E@notes.na.collabserv.com>
2017-04-22  0:12                 ` Alexey Kardashevskiy
2017-04-24  9:40                   ` Burakov, Anatoly
2017-04-21  8:51             ` gowrishankar muthukrishnan
     [not found]             ` <OF45247CC5.192F9D29-ONC1258109.002D6497-C1258109.002F2868@notes.na.collabserv.com>
2017-04-21  8:59               ` Alexey Kardashevskiy
2017-04-22 21:11 ` [dpdk-dev] [PATCH dpdk 0/5] ppc64/spapr: Attempt to use on POWER8 Olga Shern
2017-04-23 13:35   ` Alexey Kardashevskiy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20a6a7f9-ed94-0e0f-aa65-75270cbc0b2b@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=JPF@zurich.ibm.com \
    --cc=dev@dpdk.org \
    --cc=gowrishankar.m@in.ibm.com \
    --cc=olgas@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).