From: Gleb Natapov <gleb@cloudius-systems.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 0/3] Mellanox ConnectX-3 PMD
Date: Thu, 26 Feb 2015 17:03:34 +0200 [thread overview]
Message-ID: <20150226150334.GA23946@cloudius-systems.com> (raw)
In-Reply-To: <20150226141834.GX23569@6wind.com>
On Thu, Feb 26, 2015 at 03:18:34PM +0100, Adrien Mazarguil wrote:
> On Thu, Feb 26, 2015 at 03:49:07PM +0200, Gleb Natapov wrote:
> > On Thu, Feb 26, 2015 at 02:36:27PM +0100, Thomas Monjalon wrote:
> > > 2015-02-26 13:51, Gleb Natapov:
> > > > Did git pull today. After enabling mlnx pmd compilation fails with:
> > > >
> > > > dpdk/lib/librte_pmd_mlx4/mlx4.c: In function ‘mlx4_pci_devinit’:
> > > > dpdk/lib/librte_pmd_mlx4/mlx4.c:4636:14: error: too few arguments to function ‘rte_eth_dev_allocate’
> > > > eth_dev = rte_eth_dev_allocate(name);
> > >
> > > Yes, thanks for reporting.
> > > I didn't test the disabled mlx4 after hotplug integration:
> > > dpdk.org/browse/dpdk/commit/?id=9f1653e7b7e1746e7c
> > >
> > > Clearly, I have to improve my sanity checks.
> > > Sorry for the inconvenience.
> > No problem, I fixed that locally, but now I see another issue. I have
> > several PMDs statically compiled in with my application and I expect
> > dpdk to choose correct one depending on available HW, but mlnx pmd does
> > not behave nicely, if its initialization fails it kills entire
> > application:
> >
> > EAL: PCI device 0000:03:00.0 on NUMA socket 0
> > EAL: probe driver: 15b3:1003 librte_pmd_mlx4
> > EAL: Error - exiting with code: 1
> > Cause: Requested device 0000:03:00.0 cannot be used
>
> About this error, make sure you are using the kernel modules provided by the
> mlnx-ofed-kernel package from MOFED [1] as described in the documentation.
>
The problem is not in the error, I know how to get rid of it, but in the
error handling. My program has a fallback, so I an error to init a PMD
should not kill it, non other PMDs do.
--
Gleb.
next prev parent reply other threads:[~2015-02-26 15:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:20 [dpdk-dev] [PATCH 0/2] " Adrien Mazarguil
2015-01-29 15:20 ` [dpdk-dev] [PATCH 1/2] scripts: add auto-config-h.sh Adrien Mazarguil
2015-01-29 15:20 ` [dpdk-dev] [PATCH 2/2] mlx4: new poll mode driver Adrien Mazarguil
2015-01-29 15:37 ` Stephen Hemminger
2015-01-29 15:45 ` Adrien Mazarguil
2015-02-21 4:16 ` [dpdk-dev] [PATCH v2 0/4] Mellanox ConnectX-3 PMD Adrien Mazarguil
2015-02-21 4:16 ` [dpdk-dev] [PATCH v2 1/4] scripts: add auto-config-h.sh Adrien Mazarguil
2015-02-25 13:52 ` [dpdk-dev] [PATCH v3 0/3] Mellanox ConnectX-3 PMD Adrien Mazarguil
2015-02-25 13:52 ` [dpdk-dev] [PATCH v3 1/3] scripts: check features to generate configuration header Adrien Mazarguil
2015-02-25 13:52 ` [dpdk-dev] [PATCH v3 2/3] mlx4: new poll mode driver Adrien Mazarguil
2015-02-25 13:52 ` [dpdk-dev] [PATCH v3 3/3] doc: add librte_pmd_mlx4 documentation Adrien Mazarguil
2015-03-02 17:45 ` Butler, Siobhan A
2015-02-25 15:13 ` [dpdk-dev] [PATCH v3 0/3] Mellanox ConnectX-3 PMD Thomas Monjalon
2015-02-26 11:51 ` Gleb Natapov
2015-02-26 13:36 ` Thomas Monjalon
2015-02-26 13:49 ` Gleb Natapov
2015-02-26 14:18 ` Adrien Mazarguil
2015-02-26 15:03 ` Gleb Natapov [this message]
2015-02-27 18:38 ` Adrien Mazarguil
2015-03-01 11:07 ` Gleb Natapov
2015-02-21 4:17 ` [dpdk-dev] [PATCH v2 2/4] mlx4: new poll mode driver Adrien Mazarguil
2015-02-21 4:17 ` [dpdk-dev] [PATCH v2 3/4] maintainers: claim responsibility for mlx4 PMD Adrien Mazarguil
2015-02-21 4:17 ` [dpdk-dev] [PATCH v2 4/4] doc: add librte_pmd_mlx4 documentation Adrien Mazarguil
2015-03-01 11:15 ` [dpdk-dev] [PATCH 0/2] Mellanox ConnectX-3 PMD Keunhong Lee
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=20150226150334.GA23946@cloudius-systems.com \
--to=gleb@cloudius-systems.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).