From: Thomas Monjalon <thomas@monjalon.net>
To: Alex Chapman <alex.chapman@arm.com>
Cc: dev@dpdk.org, Luca.Vizzarro@arm.com, Paul.Szczepanek@arm.com,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: Re: Issue in testpmd when using RSS Flows with Mellanox NICs
Date: Wed, 31 Jul 2024 15:02:12 +0200 [thread overview]
Message-ID: <2103021.K71DO8KEF6@thomas> (raw)
In-Reply-To: <8adf2621-3202-4eff-ab9b-61cdbfc901ad@arm.com>
Hello,
31/07/2024 14:55, Alex Chapman:
> Hello maintainers,
Do not hesitate to read the file MAINTAINERS to place the appropriate Cc list.
Adding mlx5 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
next prev parent reply other threads:[~2024-07-31 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 12:55 Issue in testpmd when using RSS Flows with Mellanox NICs Alex Chapman
2024-07-31 13:02 ` Thomas Monjalon [this message]
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=2103021.K71DO8KEF6@thomas \
--to=thomas@monjalon.net \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=alex.chapman@arm.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.