From: Tom Barbette <barbette@kth.se>
To: dev@dpdk.org
Cc: Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] Cannot use MLX5 groups : cannot create jump action.: Operation not supported
Date: Sat, 30 Nov 2019 17:23:24 +0100 [thread overview]
Message-ID: <747a9c1a-8324-5e6b-69ec-55c35807c109@kth.se> (raw)
In-Reply-To: <b8ff4dc3-6b96-a0b8-d170-05313eb9d96c@kth.se>
Solved. The error was due to that NIC not having UCTX_EN enabled in the
firmware.
Maybe a less cryptic message/warning would be helpful though? DV was
enabled so I did not thought the problem could be below. A warning when
the user explicitly asks for dv_flow_en=1 but UCTX_EN is not enabled maybe?
Thanks,
Tom
Le 30/11/2019 à 12:19, Tom Barbette a écrit :
> Hi all,
>
> I'm struggling to use the group feature with MLX5.
>
> I'm using 19.08.2 for now (while
> https://bugs.dpdk.org/show_bug.cgi?id=371 gets fixed).
>
> I use the latest OFED (no inbox driver this time).
>
> I have dv_flow_en=1, but I still get "cannot create jump action.:
> Operation not supported". when I want to use the jump action or "cannot
> create table: Cannot allocate memory" when trying to add a rule to table
> 1, all of this with testpmd but my own app does not work better.
>
> sudo ~/dpdk-skylake/x86_64-native-linuxapp-gcc/app/testpmd –l 0-3 -w
> 0000:17:00.0,dv_flow_en=1 –n 6 -- -i
> EAL: Detected 36 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'VA'
> EAL: Probing VFIO support...
> EAL: PCI device 0000:17:00.0 on NUMA socket 0
> EAL: probe driver: 15b3:1017 net_mlx5
> net_mlx5: can not get IB device "mlx5_0" ports number
> Interactive-mode selected
> testpmd: create a new mbuf pool <mbuf_pool_socket_1>: n=283456,
> size=2176, socket=1
> testpmd: preferred mempool ops selected: ring_mp_mc
> testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=283456,
> size=2176, socket=0
> testpmd: preferred mempool ops selected: ring_mp_mc
>
> Warning! port-topology=paired and odd forward ports number, the last
> port will pair with itself.
>
> Configuring Port 0 (socket 0)
> Port 0: 50:6B:4B:43:8A:DA
> Checking link statuses...
> Done
> testpmd> flow create 0 group 1 ingress pattern eth / end actions queue
> index 0 / end
> Caught error type 1 (cause unspecified): cannot create table: Cannot
> allocate memory
> testpmd> flow validate 0 group 1 ingress pattern eth / end actions queue
> index 0 / end
> Flow rule validated
> testpmd> flow create 0 group 0 ingress pattern eth / end actions jump
> group 1 / end
> Caught error type 16 (specific action): cannot create jump action.:
> Operation not supported
> testpmd>
>
> Thanks,
>
> Tom
prev parent reply other threads:[~2019-11-30 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 11:19 Tom Barbette
2019-11-30 16:23 ` Tom Barbette [this message]
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=747a9c1a-8324-5e6b-69ec-55c35807c109@kth.se \
--to=barbette@kth.se \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.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 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).