From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <barbette@kth.se>
Received: from smtp-3.sys.kth.se (smtp-3.sys.kth.se [130.237.48.192])
 by dpdk.org (Postfix) with ESMTP id DB7CF4F9A
 for <users@dpdk.org>; Thu, 31 Jan 2019 17:40:56 +0100 (CET)
Received: from smtp-3.sys.kth.se (localhost.localdomain [127.0.0.1])
 by smtp-3.sys.kth.se (Postfix) with ESMTP id 8577B5A9C;
 Thu, 31 Jan 2019 17:40:56 +0100 (CET)
X-Virus-Scanned: by amavisd-new at kth.se
Received: from smtp-3.sys.kth.se ([127.0.0.1])
 by smtp-3.sys.kth.se (smtp-3.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 0Fwj38Uu6e5C; Thu, 31 Jan 2019 17:40:56 +0100 (CET)
X-KTH-Auth: barbette [83.185.86.193]
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default;
 t=1548952855; bh=BwDaMm9Wx54P7HR7Mz+R5DRR4cWmdW8jGsO5I2onjcI=;
 h=Subject:To:Cc:References:From:Date:In-Reply-To;
 b=Q8Rlhp/a8iC4T4/mIrT+sMEqeGG1b5ETAXzdQCT6rd+FnvmT1WgHNZ+gcB4nMlY4M
 6W9TGw3ePRtQuMEfMLpmJ8kaG6bekx+tNv0D9L0X9b0JJQ011FTUXt7A2pE1gZvDpB
 +CvUwCZGqMhXd2KHH5lF3MW2gRo6VuMOKWN9bpRI=
X-KTH-mail-from: barbette@kth.se
Received: from [192.168.43.44] (m83-185-86-193.cust.tele2.se [83.185.86.193])
 by smtp-3.sys.kth.se (Postfix) with ESMTPSA id 996C759E7;
 Thu, 31 Jan 2019 17:40:48 +0100 (CET)
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>
References: <26cb5e4e0840481f99d81ae8dfc28f6e@exdb05.ug.kth.se>
 <AM0PR0502MB3795616E36434242C3C3B2BBC3910@AM0PR0502MB3795.eurprd05.prod.outlook.com>
 <35494c8d-b3c1-dbef-1b0a-204db86440e8@kth.se>
 <0521a89a-2092-f24f-1e1b-89a79dd91a05@kth.se>
 <AM0PR0502MB3795470067C7FF728D3F4876C3910@AM0PR0502MB3795.eurprd05.prod.outlook.com>
From: Tom Barbette <barbette@kth.se>
Message-ID: <c8c71f77-d775-2d72-7e09-9bd4380ca74e@kth.se>
Date: Thu, 31 Jan 2019 17:40:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <AM0PR0502MB3795470067C7FF728D3F4876C3910@AM0PR0502MB3795.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-users] mlx5 flow MARK action does not work with RSS
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jan 2019 16:40:57 -0000

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