From: Shahaf Shuler <shahafs@mellanox.com>
To: Tom Barbette <barbette@kth.se>, users <users@dpdk.org>,
Raslan Darawsheh <rasland@mellanox.com>
Cc: Olga Shern <olgas@mellanox.com>, Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-users] mlx5 flow MARK action does not work with RSS
Date: Thu, 31 Jan 2019 14:04:59 +0000 [thread overview]
Message-ID: <AM0PR0502MB3795470067C7FF728D3F4876C3910@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <0521a89a-2092-f24f-1e1b-89a79dd91a05@kth.se>
Thursday, January 31, 2019 2:55 PM, Tom Barbette:
> Subject: Re: [dpdk-users] mlx5 flow MARK action does not work with RSS
>
> On 2019-01-31 09:30, Tom Barbette wrote:
> > I therefore tried different things and found that the problem was a
> > misconfiguration of the RSS action. Thanks!
> >
>
> Actually, it was because the rule installation fails when the flow is not
> classifying on "ipv4", because of the RSS parameter.
>
> testpmd> flow create 0 ingress pattern eth type is 0x0800 / end actions
> mark id 1 / rss / end
> Caught error type 1 (cause unspecified): hardware refuses to create
> flow: Invalid argument
>
> testpmd> flow create 0 ingress pattern eth type is 0x0800 / ipv4 / end
> actions mark id 1 / rss / end
> Flow rule #0 created
>
> Isn't it technically possible to have a "default" action? Mark the flow then let
> the packet be as usual?
Not sure what you mean here by packet be as usual?
That would be so much better than tracking which
> rules classify which protocol and change the action according to that... The
> NIC does it by itself already...
What is the functionally you seek? It will much help to propose a solution.
>
> Thanks,
> Tom
next prev parent reply other threads:[~2019-01-31 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 17:47 Tom Barbette
2019-01-31 6:42 ` Shahaf Shuler
2019-01-31 8:30 ` Tom Barbette
2019-01-31 12:54 ` Tom Barbette
2019-01-31 14:04 ` Shahaf Shuler [this message]
2019-01-31 16:40 ` Tom Barbette
2019-02-03 12:44 ` Shahaf Shuler
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=AM0PR0502MB3795470067C7FF728D3F4876C3910@AM0PR0502MB3795.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=barbette@kth.se \
--cc=olgas@mellanox.com \
--cc=rasland@mellanox.com \
--cc=users@dpdk.org \
--cc=yskoh@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).