From: Olga Shern <olgas@mellanox.com>
To: Bill O'Hara <billtohara@gmail.com>, "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 06:55:21 +0000 [thread overview]
Message-ID: <AM2PR05MB0995427F9B56B4D37D9AEFACD3350@AM2PR05MB0995.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CABrJh-cL0gDVX0gousX6ze36qODUvbD00KsnoctuHADVbkzrYA@mail.gmail.com>
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] 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
next prev parent reply other threads:[~2015-10-08 6: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 [this message]
2015-10-08 9:03 ` Olga Shern
2015-10-08 16:06 ` Bill O'Hara
2015-10-08 20:55 ` Bill O'Hara
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=AM2PR05MB0995427F9B56B4D37D9AEFACD3350@AM2PR05MB0995.eurprd05.prod.outlook.com \
--to=olgas@mellanox.com \
--cc=billtohara@gmail.com \
--cc=dev@dpdk.org \
/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).