From: Raslan Darawsheh <rasland@mellanox.com>
To: Tobias Urdin <tobias.urdin@crystone.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
Date: Mon, 11 Jun 2018 10:57:52 +0000 [thread overview]
Message-ID: <DB5PR05MB125470C108D244B252EC6550C2780@DB5PR05MB1254.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <0f588ff5d91447b6b985d48cfd263ff2@mb01.staff.ognet.se>
What I really want to see is the init process for OVS-DPDK that dumps the DPDK initialization.
I think you will find it at the beginning of the log that you just sent.
Kindest regards,
Raslan Darawsheh
-----Original Message-----
From: Tobias Urdin [mailto:tobias.urdin@crystone.com]
Sent: Monday, June 11, 2018 1:00 PM
To: Raslan Darawsheh <rasland@mellanox.com>
Cc: users@dpdk.org
Subject: Re: mellanox connect-x 3 pro dpdk with openvswitch
Hello Raslan,
Thank you for your reply.
For reference the br-mlx bridge was created like this:
$ovs-vsctl add-br br-mlx -- set bridge br-mlx datapath_type=netdev
$ovs-vsctl add-port br-mlx enp59s0d1 -- set Interface enp59s0d1 type=dpdk options:dpdk-devargs=mlx4_0
ovs-vsctl: Error detected while setting up 'enp59s0d1': Error attaching device 'mlx4_0' to DPDK. See ovs-vswitchd log for details.
ovs-vsctl: The default log directory is "/var/log/openvswitch".
In the ovs-vswitchd.log
2018-06-11T09:56:20.613Z|00185|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:56:20.613Z|00186|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:56:20.613Z|00187|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
Here is the complete log after restarting openvswitch-switch service:
2018-06-11T09:57:49.380Z|00134|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.9.0
2018-06-11T09:57:52.812Z|00135|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.812Z|00136|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.812Z|00137|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.825Z|00138|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.825Z|00139|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.825Z|00140|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.832Z|00141|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.832Z|00142|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.832Z|00143|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.843Z|00144|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.843Z|00145|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.843Z|00146|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.856Z|00147|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.856Z|00148|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.856Z|00149|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.862Z|00150|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.862Z|00151|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.862Z|00152|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.870Z|00153|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.870Z|00154|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.870Z|00155|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.889Z|00156|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.889Z|00157|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.889Z|00158|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.903Z|00159|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.903Z|00160|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.903Z|00161|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.908Z|00162|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.908Z|00163|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.908Z|00164|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.914Z|00165|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.914Z|00166|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.914Z|00167|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:52.923Z|00168|dpdk|ERR|EAL: Unable to find a bus for the device 'mlx4_0'
2018-06-11T09:57:52.923Z|00169|netdev_dpdk|WARN|Error attaching device 'mlx4_0' to DPDK
2018-06-11T09:57:52.923Z|00170|netdev|WARN|enp59s0d1: could not set configuration (Invalid argument)
2018-06-11T09:57:54.808Z|00171|memory|INFO|1406100 kB peak resident set size after 10.1 seconds
2018-06-11T09:57:54.808Z|00172|memory|INFO|handlers:118 ofconns:3
ports:8 revalidators:42 rules:36 udpif keys:1
2018-06-11T09:58:02.850Z|00173|connmgr|INFO|br-int<->tcp:127.0.0.1:6633:
5 flow_mods 10 s ago (5 adds)
2018-06-11T09:58:02.898Z|00174|connmgr|INFO|br-ex<->tcp:127.0.0.1:6633:
2 flow_mods 10 s ago (2 adds)
2018-06-11T09:58:02.930Z|00175|connmgr|INFO|br-tun<->tcp:127.0.0.1:6633:
12 flow_mods 10 s ago (12 adds)
Was that what you mean by init log?
Best regards
On 06/11/2018 11:51 AM, Raslan Darawsheh wrote:
> Hi Tobias,
>
> Can you try using the following ?
>
> ovs-vsctl add-port br-mlx enp59s0d1 -- set Interface enp59s0d1
> type=dpdk options:dpdk-devargs=mlx4_0
>
> if it didn't work can you send the OVS-DPDK init log ?
>
> Kindest regards,
> Raslan Darawsheh
>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Tobias Urdin
> Sent: Monday, June 11, 2018 12:15 PM
> To: users@dpdk.org
> Subject: [dpdk-users] mellanox connect-x 3 pro dpdk with openvswitch
>
> 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 prev parent reply other threads:[~2018-06-11 10:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 9:15 Tobias Urdin
2018-06-11 9:51 ` Raslan Darawsheh
2018-06-11 9:59 ` Tobias Urdin
2018-06-11 10:57 ` Raslan Darawsheh [this message]
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=DB5PR05MB125470C108D244B252EC6550C2780@DB5PR05MB1254.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=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).