DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Bill O'Hara" <billtohara@gmail.com>
To: Olga Shern <olgas@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Mellanox PMD failure w/DPDK-2.1.0 and MLNX_OFED-3.1-1.0.3
Date: Thu, 8 Oct 2015 13:55:11 -0700	[thread overview]
Message-ID: <CABrJh-dgtVya=FZv9zn7UpaJCt_zHw6T-r7Rjjd2Z3eNOpdN7w@mail.gmail.com> (raw)
In-Reply-To: <CABrJh-eNOw-_=aGu2CfCV-tJvk_3Kv2aYgPmLij1_XZfx+5j4A@mail.gmail.com>

Olga

If it's all all helpful, linking our code against dpdk-2.0 and (statically)
against the appropriate custom-built libibverbs that we used with it, works
on those machines. There is of course no call to ibv_exp_create_res_domain()
in that version of the library. But it at least confirms basic operation of
the upgraded OFED and firmware on those boxes.

Is there anything else we can check or confirm for you?

thanks
bill


On Thu, Oct 8, 2015 at 9:06 AM, Bill O'Hara <billtohara@gmail.com> wrote:

> Hi Olga
>
> Firmware is version 2.35.5100. Configuration details below.
>
> Thanks for any hints.
> bill
>
> root:~# cat /etc/modprobe.d/mlx4_core.conf
> options mlx4_core port_type_array=2,2 num_vfs=16 probe_vf=4
>
> root:~# ibstat
> CA 'mlx4_0'
> CA type: MT4099
> Number of ports: 1
> Firmware version: 2.35.5100
> Hardware version: 1
> Node GUID: 0xf4521403008f1680
> System image GUID: 0xf4521403008f1683
> Port 1:
> State: Active
> Physical state: LinkUp
> Rate: 56
> Base lid: 0
> LMC: 0
> SM lid: 0
> Capability mask: 0x0c010000
> Port GUID: 0xf65214fffe8f1680
> Link layer: Ethernet
> CA 'mlx4_1'
> CA type: MT4100
> Number of ports: 1
> Firmware version: 2.35.5100
> Hardware version: 1
> Node GUID: 0x00140500c2d3b05f
> System image GUID: 0xf4521403008f1683
> Port 1:
> State: Active
> Physical state: LinkUp
> Rate: 56
> Base lid: 0
> LMC: 0
> SM lid: 0
> Capability mask: 0x0c010000
> Port GUID: 0xfc9739fffe1272c3
> Link layer: Ethernet
> CA 'mlx4_2'
> CA type: MT4100
> Number of ports: 1
> Firmware version: 2.35.5100
> Hardware version: 1
> Node GUID: 0x00140500b90af10c
> System image GUID: 0xf4521403008f1683
> Port 1:
> State: Active
> Physical state: LinkUp
> Rate: 56
> Base lid: 0
> LMC: 0
> SM lid: 0
> Capability mask: 0x0c010000
> Port GUID: 0x20ecbbfffeefb934
> Link layer: Ethernet
> CA 'mlx4_3'
> CA type: MT4100
> Number of ports: 1
> Firmware version: 2.35.5100
> Hardware version: 1
> Node GUID: 0x001405009661e607
> System image GUID: 0xf4521403008f1683
> Port 1:
> State: Active
> Physical state: LinkUp
> Rate: 56
> Base lid: 0
> LMC: 0
> SM lid: 0
> Capability mask: 0x0c010000
> Port GUID: 0xf4c8e6fffe5abc89
> Link layer: Ethernet
> CA 'mlx4_4'
> CA type: MT4100
> Number of ports: 1
> Firmware version: 2.35.5100
> Hardware version: 1
> Node GUID: 0x00140500bd09e128
> System image GUID: 0xf4521403008f1683
> Port 1:
> State: Active
> Physical state: LinkUp
> Rate: 56
> Base lid: 0
> LMC: 0
> SM lid: 0
> Capability mask: 0x0c010000
> Port GUID: 0x5828e1fffe34f919
> Link layer: Ethernet
>
> On Thu, Oct 8, 2015 at 2:03 AM, Olga Shern <olgas@mellanox.com> wrote:
>
>> Hi Bill,
>>
>> Can you please check the fw version that is installed on your ConnectX3?
>>
>> Thanks
>>
>>
>> Sent from Samsung Mobile.
>>
>>
>> -------- Original message --------
>> From: Olga Shern
>> Date:08/10/2015 7:55 AM (GMT+00:00)
>> To: Bill O'Hara ,dev@dpdk.org
>> Subject: RE: [dpdk-dev] Mellanox PMD failure w/DPDK-2.1.0 and
>> MLNX_OFED-3.1-1.0.3
>>
>> Hi Bill,
>>
>> There shouldn’t be any problem with what you are doing.
>> We are checking this now.
>>
>> Best Regards,
>> Olga
>>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org <dev-bounces@dpdk.org>] On Behalf
>> Of Bill O'Hara
>> Sent: Thursday, October 08, 2015 6:05 AM
>> To: dev@dpdk.org
>> Subject: [dpdk-dev] Mellanox PMD failure w/DPDK-2.1.0 and
>> MLNX_OFED-3.1-1.0.3
>>
>> Hello
>>
>> I wonder if anyone can suggest why previously working dpdk code may fail
>> in the Mellanox pmd code in dpdk-2.1.0, seemingly due to failure to create
>> a "resource domain" via ibv_exp_create_res_domain(). I must admit I haven't
>> seen that verb before, and it appears to be returning null with no error
>> message.
>>
>> The DPDK log gives these hints:
>>
>> PMD: librte_pmd_mlx4: 0xa4fc20: TX queues number update: 0 -> 1
>> PMD: librte_pmd_mlx4: 0xa4fc20: RX queues number update: 0 -> 1
>> PMD: librte_pmd_mlx4: 0xa4fc20: RD creation failure: Cannot allocate
>> memory
>>
>> I'm using dpdk-2.10.0 and  MLNX_OFED_LINUX-3.1-1.0.3 on ubuntu14.04 with a
>> connectx-3 card.
>>
>> thanks
>> bill
>>
>
>

  reply	other threads:[~2015-10-08 20:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-08  3:04 Bill O'Hara
2015-10-08  6:55 ` Olga Shern
2015-10-08  9:03   ` Olga Shern
2015-10-08 16:06     ` Bill O'Hara
2015-10-08 20:55       ` Bill O'Hara [this message]
2015-10-08 22:27         ` Olga Shern
2015-10-09 21:17           ` Bill O'Hara
2015-10-15 12:50             ` Olga Shern
2015-10-16 19:11               ` Bill O'Hara
2015-10-16 20:01                 ` Stephen Hemminger
2015-10-17 19:10                 ` Olga Shern
2015-10-28  2:32 Dave Engebretsen

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='CABrJh-dgtVya=FZv9zn7UpaJCt_zHw6T-r7Rjjd2Z3eNOpdN7w@mail.gmail.com' \
    --to=billtohara@gmail.com \
    --cc=dev@dpdk.org \
    --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).