From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: "Peng, Yuan" <yuan.peng@intel.com>
Cc: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] a doubt about rss types action in rte_flow
Date: Wed, 7 Nov 2018 10:54:00 +0100 [thread overview]
Message-ID: <20181107095400.GI4638@6wind.com> (raw)
In-Reply-To: <67D543A150B29E4CAAE53918F64EDAEA37627F5A@SHSMSX103.ccr.corp.intel.com>
Hi and sorry for the delay.
On Thu, Oct 18, 2018 at 06:42:52AM +0000, Peng, Yuan wrote:
> Hi Adrien,
>
> I have a doubt about the action rss types in rte_flow.
> testpmd> flow create 0 ingress pattern end actions rss types end / end
>
> what is the expected function of the command?
> Does it mean enable RSS in no types? So actually it can disable rss all?
Doing so requests whatever counts as default RSS from the driver as
documented in doc/guides/prog_guide/rte_flow.rst:
"Unlike global RSS settings used by other DPDK APIs, unsetting the ``types``
field does not disable RSS in a flow rule. Doing so instead requests safe
unspecified "best-effort" settings from the underlying PMD, which depending
on the flow rule, may result in anything ranging from empty (single queue)
to all-inclusive RSS."
> There are different execution result of the command from our different NICs.
> Some NICs report error:
> Caught error type 2 (flow rule (handle)): Failed to create flow.: Invalid argument
> With some NICs, the command can be executed successfully, and disable rss function for all packet types.
>
> Could you help to solve my questions?
PMDs must handle it as described by the documentation, 0 being the only safe
value applications can rely on regardless of device properties; applications
that just want traffic to be spread somehow among the queues they configured
instead of a single queue.
Therefore PMDs that currently reject it should be fixed.
--
Adrien Mazarguil
6WIND
prev parent reply other threads:[~2018-11-07 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 6:42 Peng, Yuan
2018-11-07 9:54 ` Adrien Mazarguil [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=20181107095400.GI4638@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=wei.zhao1@intel.com \
--cc=yuan.peng@intel.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).