From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Sam <batmanustc@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Under Ovs-2.8.0 + DPDK-17.05-rc1, can't add port which using mlx5 driver onto bridge br0
Date: Wed, 28 Mar 2018 14:49:02 +0200 [thread overview]
Message-ID: <20180328124902.jhbwpax4ufx7yslp@laranjeiro-vm.dev.6wind.com> (raw)
In-Reply-To: <CAOE=1Z2sEiTsxNoXCMAwtkBZ+=RaBynY9Vrb0xDvCSgK0Fn=MA@mail.gmail.com>
On Wed, Mar 28, 2018 at 08:20:00PM +0800, Sam wrote:
> Hi all,
>
> I'm using Ovs-2.8.0 + DPDK-17.05-rc1 with two netdev using mlx5 driver,
> like this:
>
> $ sudo /usr/local/share/openvswitch/scripts/dpdk_nic_bind --status
> > Network devices using DPDK-compatible driver
> > ============================================
> > <none>
> > Network devices using kernel driver
> > ===================================
> > ...
> > 0000:03:00.0 'MT27640 Family' if=eth4 drv=mlx5_core unused=igb_uio
> > 0000:03:00.1 'MT27640 Family' if=eth5 drv=mlx5_core unused=igb_uio
> > 0000:03:00.2 'MT27641 Family' if=enp3s0f2 drv=mlx5_core unused=igb_uio
> > *Active*
> > ...
> > =====================
> > <none>
>
>
> When I start ovs-vswitchd, and add port onto br0, I got errors like this:
>
> libibverbs: Warning: no userspace device-specific driver found for
> > /sys/class/infiniband_verbs/uverbs2
>
>
> and git errors in ovs-vswitchd.log like this:
>
> 2018-03-28T09:34:25.687Z|00120|dpdk|INFO|EAL: PCI device 0000:03:00.0 on
> > NUMA socket 0
> > 2018-03-28T09:34:25.687Z|00121|dpdk|INFO|EAL: probe driver: 15b3:1017
> > net_mlx5
> > 2018-03-28T09:34:25.687Z|00122|dpdk|WARN|EAL: Requested device
> > 0000:03:00.0 cannot be used
> > 2018-03-28T09:34:25.687Z|00123|dpdk|ERR|EAL: Driver cannot attach the
> > device (0000:03:00.0)
> > 2018-03-28T09:34:25.687Z|00124|netdev_dpdk|WARN|Error attaching device
> > '0000:03:00.0' to DPDK
> > 2018-03-28T09:34:25.687Z|00125|netdev|WARN|dpdk0: could not set
> > configuration (Invalid argument)
>
>
> How to fix this bug? Is there anyone got these errors? Thank you~
Hi,
I would say you don't have the correct Linux drivers, nor libraries to
make it work with DPDK.
Did you installed Mellanox OFED? If not take a look at section 19.5.
Prerequisites of the NIC documentation [1].
Regards,
[1] https://dpdk.org/doc/guides-17.05/nics/mlx5.html
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2018-03-28 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 12:20 Sam
2018-03-28 12:49 ` Nélio Laranjeiro [this message]
2018-03-29 2:03 ` Sam
2018-03-29 2:29 ` Sam
2018-03-29 7:00 ` Sam
2018-04-04 7:42 ` Nélio Laranjeiro
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=20180328124902.jhbwpax4ufx7yslp@laranjeiro-vm.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=batmanustc@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).