DPDK usage discussions
 help / color / mirror / Atom feed
From: Tom Barbette <barbette@kth.se>
To: Shahaf Shuler <shahafs@mellanox.com>, 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 17:40:38 +0100	[thread overview]
Message-ID: <c8c71f77-d775-2d72-7e09-9bd4380ca74e@kth.se> (raw)
In-Reply-To: <AM0PR0502MB3795470067C7FF728D3F4876C3910@AM0PR0502MB3795.eurprd05.prod.outlook.com>

Le 31/01/2019 à 15:04, Shahaf Shuler a écrit :
> What is the functionally you seek? It will much help to propose a solution.


What I'd like is to mark some packets. Eg ARP packets with 1, ICMP PING 
with 2, IP dst port 80 with 3, etc.

But I'd like the packets to follow the normal behavior except from that. 
My default behavior would be to use RSS to dispatch packets among a set 
of queues.

In the current scheme, I must set a specific "fate" action for each 
flow, like QUEUE or RSS.
Of course the list of flows is dynamically generated, and it is 
complicated to change QUEUE/RSS according to the flow type. I would like 
to say "mark packets, then do as the NIC would normally do". That's why 
I imagine a "default" action.


Thanks,
Tom

  reply	other threads:[~2019-01-31 16:40 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
2019-01-31 16:40         ` Tom Barbette [this message]
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=c8c71f77-d775-2d72-7e09-9bd4380ca74e@kth.se \
    --to=barbette@kth.se \
    --cc=olgas@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=shahafs@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).