From: Tobias Urdin <tobias.urdin@crystone.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
Date: Mon, 11 Jun 2018 09:15:26 +0000 [thread overview]
Message-ID: <ab8f7f8952134a21832214f7a7260368@mb01.staff.ognet.se> (raw)
Hello,
I'm stuck trying to test DPDK with a Mellanox Connect-X 3 Pro card on Ubuntu 16.04
I've enabled iommu, fixed hugepages and has installed and are running the openvswitch-switch-dpdk alternative.
$lspci | grep -i mellanox
3b:00.0 Ethernet controller: Mellanox Technologies MT27520 Family [ConnectX-3 Pro]
$lsmod | grep -i mlx
mlx4_en 110592 0
vxlan 49152 2 i40e,mlx4_en
mlx4_core 286720 1 mlx4_en
ptp 20480 3 igb,i40e,mlx4_en
$cat /etc/modprobe.d/mlx4_core.conf
options mlx4_core log_num_mgm_entry_size=-1
$ovs-vsctl add-port br-mlx dpdk0 -- set Interface dpdk0 type=dpdk
Bridge br-mlx
Port "dpdk0"
Interface "dpdk0"
type: dpdk
error: "'dpdk0' is missing 'options:dpdk-devargs'. The old 'dpdk<port_id>' names are not supported"
$ovs-vsctl add-port br-mlx enp59s0d1 -- set Interface enp59s0d1 type=dpdk options:dpdk-devargs=0000:3b:00.0,1
ovs-vsctl: Error detected while setting up 'enp59s0d1': Error attaching device '0000:3b:00.0,1' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
2018-06-11T09:10:38.696Z|00177|netdev_dpdk|WARN|Error attaching device '0000:3b:00.0,1' to DPDK
2018-06-11T09:10:38.696Z|00178|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:12:50.994Z|00181|dpdk|ERR|EAL: Driver cannot attach the device (0000:3b:00.0)
2018-06-11T09:12:50.994Z|00182|dpdk|ERR|EAL: No port found for device (0000:3b:00.0)
2018-06-11T09:12:50.994Z|00183|netdev_dpdk|WARN|Error attaching device '0000:3b:00.0,1' to DPDK
2018-06-11T09:12:50.994Z|00184|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
$ovs-vsctl add-port br-mlx dpdk0 -- set Interface dpdk0 type=dpdk options:dpdk-devargs="class=eth,mac=ec:0d:9a:b0:13:21"
ovs-vsctl: Error detected while setting up 'dpdk0': Error attaching device 'class=eth,mac=ec:0d:9a:b0:13:21' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
Port "dpdk0"
Interface "dpdk0"
type: dpdk
options: {dpdk-devargs="class=eth,mac=ec:0d:9a:b0:13:21"}
error: "Error attaching device 'class=eth,mac=ec:0d:9a:b0:13:21' to DPDK"
Anybody know what I might have missed? I have tried restarting the openvswitch services after adding the interfaces as well but no difference.
The logs doesn't say anything interesting from what I can see :(
Best regards
next reply other threads:[~2018-06-11 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 9:15 Tobias Urdin [this message]
2018-06-11 9:51 ` Raslan Darawsheh
2018-06-11 9:59 ` Tobias Urdin
2018-06-11 10:57 ` Raslan Darawsheh
2018-06-11 11:15 ` Tobias Urdin
2018-06-11 11:19 ` Raslan Darawsheh
2018-06-11 11:34 ` Tobias Urdin
2018-06-11 11:37 ` Raslan Darawsheh
2018-06-11 11:45 ` Tobias Urdin
2018-06-11 11:51 ` Raslan Darawsheh
2018-06-11 12:05 ` Tobias Urdin
2018-06-11 12:07 ` Raslan Darawsheh
2018-06-11 12:14 ` Tobias Urdin
2018-06-12 7:13 ` Raslan Darawsheh
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=ab8f7f8952134a21832214f7a7260368@mb01.staff.ognet.se \
--to=tobias.urdin@crystone.com \
--cc=users@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).