From: Ori Kam <orika@mellanox.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
Cliff Burdick <shaklee3@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] flow_filtering failed on mlx5
Date: Mon, 5 Nov 2018 13:18:22 +0000 [thread overview]
Message-ID: <AM4PR05MB3425C04B859E465ED2D8FADADBCA0@AM4PR05MB3425.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <DB7PR05MB4426BA4EC40D79DA2DA94445C3CA0@DB7PR05MB4426.eurprd05.prod.outlook.com>
Hi Cliff,
There was an issue I solved it, and submitted relevant patches.
You can look at them:
http://patches.dpdk.org/patch/47806/
http://patches.dpdk.org/patch/47807/
Best,
Ori
> -----Original Message-----
> From: Shahaf Shuler
> Sent: Monday, November 5, 2018 9:10 AM
> To: Cliff Burdick <shaklee3@gmail.com>; users <users@dpdk.org>; Ori Kam
> <orika@mellanox.com>
> Subject: RE: [dpdk-users] flow_filtering failed on mlx5
>
> +Ori the maintainer of the example code.
>
> Saturday, November 3, 2018 5:31 AM, Cliff Burdick:
> > Subject: [dpdk-users] flow_filtering failed on mlx5
> >
> > Hi I'm trying to run the flow_filtering example on a connectx-5, and it seems
> > to fail with dpdk 18.08:
> >
> > $ sudo ./build/flow -l 1 -n 1
> > EAL: Detected 48 lcore(s)
> > EAL: Detected 2 NUMA nodes
> > EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> > EAL: Probing VFIO support...
> > EAL: PCI device 0000:01:00.0 on NUMA socket 0
> > EAL: probe driver: 15b3:1013 net_mlx5
> > EAL: PCI device 0000:01:00.1 on NUMA socket 0
> > EAL: probe driver: 15b3:1013 net_mlx5
> > EAL: PCI device 0000:81:00.0 on NUMA socket 1
> > EAL: probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:81:00.1 on NUMA socket 1
> > EAL: probe driver: 8086:1528 net_ixgbe
> > EAL: PCI device 0000:82:00.0 on NUMA socket 1
> > EAL: probe driver: 15b3:1013 net_mlx5
> > EAL: PCI device 0000:82:00.1 on NUMA socket 1
> > EAL: probe driver: 15b3:1013 net_mlx5
> > :: warn: 5 ports detected, but we use only one: port 0
> > :: initializing port: 0
> > Ethdev port_id=0 requested Tx offloads 0x3f doesn't match Tx offloads
> > capabilities 0xc86af in rte_eth_dev_configure()
> > EAL: Error - exiting with code: 1
> > Cause: :: cannot configure device: err=-22, port=0
> >
> >
> > Has anyone got this to work?
next prev parent reply other threads:[~2018-11-05 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 3:30 Cliff Burdick
2018-11-05 7:10 ` Shahaf Shuler
2018-11-05 13:18 ` Ori Kam [this message]
2018-11-05 13:41 ` Cliff Burdick
2018-11-05 13:54 ` Ori Kam
2018-11-05 13:56 ` Cliff Burdick
2018-11-05 14:05 ` Ori Kam
2018-11-05 19:42 ` Cliff Burdick
2018-11-06 1:18 ` Cliff Burdick
2018-11-06 6:37 ` Ori Kam
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=AM4PR05MB3425C04B859E465ED2D8FADADBCA0@AM4PR05MB3425.eurprd05.prod.outlook.com \
--to=orika@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=shaklee3@gmail.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).