From: Muhammad Uzair Jawaid <uzair@dreambigsemi.com>
To: "asafp@nvidia.com" <asafp@nvidia.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Jump action not working on VF Connectx6dx DPDk22.11
Date: Fri, 17 Feb 2023 07:45:12 +0000 [thread overview]
Message-ID: <DM6PR22MB20609762AB326D612A080741C1A19@DM6PR22MB2060.namprd22.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hi,
I am trying to apply jump action on VF, but the testpmd giving error Operation not supported .
sudo ./build/app/dpdk-testpmd -l 4,6 -a 04:01.2 --file-prefix=ha -- -i --rxq=16 --txq=16 --disable-rss
EAL: Detected CPU lcores: 8
EAL: Detected NUMA nodes: 2
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/ha/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: VFIO support initialized
EAL: Probe PCI driver: mlx5_pci (15b3:101e) device: 0000:04:01.2 (socket 0)
TELEMETRY: No legacy callbacks, legacy socket not created
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, 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: 92:DE:11:0C:B9:32
Checking link statuses...
Done
testpmd> flow create 0 ingress pattern eth src is 00:45:67:89:ab:cd / ipv4 / end actions jump group 1 / end
port_flow_complain(): Caught PMD error type 16 (specific action): cannot create jump action.: Operation not supported
testpmd>
Can you please guide me how to apply jump action on VF?
Card Connectx6dx
DPDK 22.11/ DPDK 21.11
OFED MLNX_OFED_LINUX-5.8-1.1.2.1
Best Regards
Muhammad Uzair Jawaid
[-- Attachment #2: Type: text/html, Size: 3588 bytes --]
next reply other threads:[~2023-02-19 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 7:45 Muhammad Uzair Jawaid [this message]
2023-02-19 6:40 ` Asaf Penso
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=DM6PR22MB20609762AB326D612A080741C1A19@DM6PR22MB2060.namprd22.prod.outlook.com \
--to=uzair@dreambigsemi.com \
--cc=asafp@nvidia.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).