From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Royce Niu <royceniu@gmail.com>
Cc: dev@dpdk.org
Subject: Re: Cannot use MLX4 with igb_uio driver
Date: Mon, 9 Jan 2017 17:13:26 +0100 [thread overview]
Message-ID: <20170109161326.GD12822@6wind.com> (raw)
In-Reply-To: <CAOwUCNviASWFcbtDqaUovkN9HUtk-p8zijAFcFm9AyCYAzVh_g@mail.gmail.com>
On Mon, Jan 09, 2017 at 11:23:56PM +0800, Royce Niu wrote:
> Hi, Adrien,
>
> Actually, I tested using the original kernel module without binding. It
> works.
>
> However, it is only 6Mpps for 64B in pkt-gen, which is so slow for a 40Gbps
> NIC.
>
> Is that right?
That's difficult to say without knowing your specific setup or application,
however 6 Mpps seems abnormally slow assuming testpmd performing basic I/O
forwarding using a single thread and two ports.
> On Mon, Jan 9, 2017 at 11:13 PM, Adrien Mazarguil <
> adrien.mazarguil@6wind.com> wrote:
>
> > Hi Royce,
> >
> > On Mon, Jan 09, 2017 at 10:53:37PM +0800, Royce Niu wrote:
> > > Dear all,
> > >
> > > I cannot use my Mellanox 3 Pro, after I binded it with igb_uio driver.
> > >
> > > It always shows when I use my DPDK application.
> > >
> > > EAL: Detected 32 lcore(s)
> > > EAL: Probing VFIO support...
> > > PMD: bnxt_rte_pmd_init() called for (null)
> > > EAL: PCI device 0000:02:00.0 on NUMA socket 0
> > > EAL: probe driver: 8086:1521 rte_igb_pmd
> > > EAL: PCI device 0000:02:00.1 on NUMA socket 0
> > > EAL: probe driver: 8086:1521 rte_igb_pmd
> > > EAL: PCI device 0000:02:00.2 on NUMA socket 0
> > > EAL: probe driver: 8086:1521 rte_igb_pmd
> > > EAL: PCI device 0000:02:00.3 on NUMA socket 0
> > > EAL: probe driver: 8086:1521 rte_igb_pmd
> > > EAL: PCI device 0000:81:00.0 on NUMA socket 1
> > > EAL: probe driver: 15b3:1007 librte_pmd_mlx4
> > > PMD: librte_pmd_mlx4: cannot access device, is mlx4_ib loaded?
> > > EAL: Error - exiting with code: 1
> > > Cause: Cannot create mbuf pool
> > >
> > > ---------------
> > > I have added CONFIG_RTE_LIBRTE_MLX4_PMD=y in .config, and
> > > install MLNX_OFED_LINUX-3.4-2.0.0.0.
> >
> > The mlx4 PMD does not operate through igb_uio (see mlx4 documentation [1]),
> > PCI devices must remain bound to their original kernel module (mlx4_core),
> > however you have to additionally load mlx4_ib, mlx4_en and ib_uverbs [2].
> >
> > [1] http://dpdk.org/doc/guides/nics/mlx4.html
> > [2] http://dpdk.org/doc/guides/nics/mlx4.html#prerequisites
> >
> > --
> > Adrien Mazarguil
> > 6WIND
> >
>
>
>
> --
> Regards,
>
> Royce
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2017-01-09 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 14:53 Cannot use MLX4 with igb_uio driver Royce Niu
2017-01-09 15:13 ` Adrien Mazarguil
2017-01-09 15:23 ` Royce Niu
2017-01-09 16:13 ` Adrien Mazarguil [this message]
2017-01-09 16:57 ` Royce Niu
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=20170109161326.GD12822@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=royceniu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.