From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] dpaa2-eth: Make Rx flow hash key configurable Date: Mon, 24 Sep 2018 12:29:15 -0700 (PDT) Message-ID: <20180924.122915.506780899873501609.davem@davemloft.net> References: <20180924153611.25179-1-ruxandra.radulescu@nxp.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, ioana.ciornei@nxp.com To: ruxandra.radulescu@nxp.com Return-path: Received: from shards.monkeyblade.net ([23.128.96.9]:51198 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728608AbeIYBc7 (ORCPT ); Mon, 24 Sep 2018 21:32:59 -0400 In-Reply-To: <20180924153611.25179-1-ruxandra.radulescu@nxp.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Ioana Ciocoi Radulescu Date: Mon, 24 Sep 2018 15:36:21 +0000 > Until now, the Rx flow hash key was a 5-tuple (IP src, IP dst, > IP nextproto, L4 src port, L4 dst port) fixed value that we > configured at probe. > > Add support for configuring this hash key at runtime. > We support all standard header fields configurable through ethtool, > but cannot differentiate between flow types, so the same hash key > is applied regardless of protocol. > > We also don't support the discard option. > > Signed-off-by: Ioana Radulescu Applied.