From: Alex Chapman <alex.chapman@arm.com>
To: dev@dpdk.org
Cc: Luca.Vizzarro@arm.com, Paul.Szczepanek@arm.com
Subject: Issue in testpmd when using RSS Flows with Mellanox NICs
Date: Wed, 31 Jul 2024 13:55:47 +0100 [thread overview]
Message-ID: <8adf2621-3202-4eff-ab9b-61cdbfc901ad@arm.com> (raw)
Hello maintainers,
I am currently facing issues when creating RSS flows using testpmd.
When using the following flow on an intel NIC, it works as expected,
using the reta table to redirect ipv4-udp packets to the correct queue.
flow create 0 ingress pattern eth / ipv4 / udp / end actions rss types
ipv4-udp end queues end func toeplitz / end
However when executing the same command on a Mellanox NIC, the following
error occurs.
Caught PMD error type 15 (action configuration): No queues
configured: Invalid argument
This error can be resolved by manually specifying the queues used:
flow create 0 ingress pattern eth / ipv4 / udp / end actions rss
types ipv4-udp end queues 0 1 2 3 4 5 6 7 8 end func toeplitz / end
However the packets are not placed into their expected queues using the
reta table.
When looking through the Generic flow API guide under RSS
(https://doc.dpdk.org/guides/prog_guide/rte_flow.html), the attribute
queues does not exist.
From my understanding this seems to be a mistake, as the attribute
"queue" does exist with the definition "queue indices to use"
However when attempting to use this attribute I get the error "Bad
arguments"
If anyone is able to shed some light on the use of RSS in flows, that
would be greatly appreciated.
Thanks,
Alex
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next reply other threads:[~2024-07-31 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 12:55 Alex Chapman [this message]
2024-07-31 13:02 ` Thomas Monjalon
2024-08-01 12:13 ` Dariusz Sosnowski
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=8adf2621-3202-4eff-ab9b-61cdbfc901ad@arm.com \
--to=alex.chapman@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=dev@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).