From: Tom Barbette <barbette@kth.se>
To: users <users@dpdk.org>
Cc: Shahaf Shuler <shahafs@mellanox.com>
Subject: [dpdk-users] mlx5 flow MARK action does not work with RSS
Date: Wed, 30 Jan 2019 17:47:15 +0000 [thread overview]
Message-ID: <26cb5e4e0840481f99d81ae8dfc28f6e@exdb05.ug.kth.se> (raw)
Hi all,
It seems that when using the RTE_FLOW_ACTION_TYPE_RSS action, the RTE_FLOW_ACTION_TYPE_MARK does not work anymore with mlx5. The flag RX_PKT_ID is not set, and the value in .hi is not good either. If I use RTE_FLOW_ACTION_TYPE_QUEUE it works fine.
Actually, I do not want specifically to use the RSS action. I would just like the packet to be marked but continue its normal path (that is the global RSS). However I get the "no fate action" error in that case.
Any way to use RSS but keep the "mark" ?
Thanks,
Tom
next reply other threads:[~2019-01-30 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 17:47 Tom Barbette [this message]
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
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=26cb5e4e0840481f99d81ae8dfc28f6e@exdb05.ug.kth.se \
--to=barbette@kth.se \
--cc=shahafs@mellanox.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).