From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-4.sys.kth.se (smtp-4.sys.kth.se [130.237.48.193]) by dpdk.org (Postfix) with ESMTP id 2B0911B427 for ; Thu, 31 Jan 2019 13:54:55 +0100 (CET) Received: from smtp-4.sys.kth.se (localhost.localdomain [127.0.0.1]) by smtp-4.sys.kth.se (Postfix) with ESMTP id BEB8ED40; Thu, 31 Jan 2019 13:54:54 +0100 (CET) X-Virus-Scanned: by amavisd-new at kth.se Received: from smtp-4.sys.kth.se ([127.0.0.1]) by smtp-4.sys.kth.se (smtp-4.sys.kth.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SfNApc3P7PC7; Thu, 31 Jan 2019 13:54:51 +0100 (CET) X-KTH-Auth: barbette [130.237.20.142] DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kth.se; s=default; t=1548939291; bh=rG9oFfRgC3QdXdAChEUAxnNRsQcTNXzVUuM1ALwduZ0=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=UNF3rGyj+ltgkatRRF+i+6A2JDr0cwQHMSJI6ns7Rh8so1V5xH5IeNl71aRF0PfRn 5EQPaJVTazNXiYImILheeYmwf5f5opyjWVBRt2caFMYihHDBAVa3J22ZBwYQDKlPwW UCxv9+zZyiUvpKd47MTkGE76OgnlfIh3aGcU4kPE= X-KTH-mail-from: barbette@kth.se Received: from [130.237.20.142] (s2587.it.kth.se [130.237.20.142]) by smtp-4.sys.kth.se (Postfix) with ESMTPSA id C960E2C53; Thu, 31 Jan 2019 13:54:50 +0100 (CET) From: Tom Barbette To: Shahaf Shuler , users , Raslan Darawsheh Cc: Olga Shern , Yongseok Koh References: <26cb5e4e0840481f99d81ae8dfc28f6e@exdb05.ug.kth.se> <35494c8d-b3c1-dbef-1b0a-204db86440e8@kth.se> Message-ID: <0521a89a-2092-f24f-1e1b-89a79dd91a05@kth.se> Date: Thu, 31 Jan 2019 13:54:50 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <35494c8d-b3c1-dbef-1b0a-204db86440e8@kth.se> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2019 12:54:55 -0000 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? 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... Thanks, Tom