Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp369531yba; Wed, 8 May 2019 22:28:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqx78VE1/HKVE6m2ZOQ+vt9HtwITjmwCCFiKU5S9Qt0rxggoq1Z3gNrqoXYE89K4tc8L+jTK X-Received: by 2002:a63:243:: with SMTP id 64mr3041512pgc.214.1557379687098; Wed, 08 May 2019 22:28:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557379687; cv=none; d=google.com; s=arc-20160816; b=tWseYgTVxuCJna3VgYxPnWWmNaWEbtKnDpDZtvQ/jkeM23jDygnkwRFxTIJPtwwDkK VrPR4iLPPHxr/WNRCDxfZixeA+7xEEElI1DrNUy4MruDsWh6w08lPylpftzLF9dmBuiK kS/7KFoUP0bI2z/zU/3/6J2KbP4+BvzrttcwPf0ANk3ObDalTmBLYfn6EDZ/2ZvVxHP+ ay6VI8zgEmmB1BuSF9KGEC5NoCJlnxQx027ddCbOwmRYVcq/F8yK+EXcNwr6gGyrh1zl AM/0UQ6lOOM6YALZBhIwDCqorWe1YPsHDqTXujEcu5+bav7i5DwmFFcMXrSPADpp8ChD LF6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=/42cwvZ83L36schii218iPAMEFpvzAi7FRkDYOWYekw=; b=mXCqOLg4Y6XjEpupPspEdUqdML2sBUymclVO1tHlnAuoXb0bwMX2WXMbAvHWSmXaI8 FEGY89xUHaTRo3tQeOl6lz+9c3p0VXTZkP3AabyIUnFW1RXKnWZe91fMymYZ28/5LqSt dXFYYp8eB2CrasnDK8tdVnSQIaY8emn7yojJSBHtMwVvCZ6UpvO45RwmhnWCB7W80CQj vrJ0JGdvrQShtsHyqpFBdEYsEzcwB03B0vNrDgerqmE2hNeO4LV3bDsPQNU9JC6oab3Y y+S7VUyRoQ+BynCfGI0u+1C2ZYJWwlH1I8aOOAxSHi77LZdzLyCyO/KwZ7O+1YhqhM/2 xSeg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a11si1395470pfn.52.2019.05.08.22.27.51; Wed, 08 May 2019 22:28:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728834AbfEIFOP (ORCPT + 99 others); Thu, 9 May 2019 01:14:15 -0400 Received: from relay12.mail.gandi.net ([217.70.178.232]:43967 "EHLO relay12.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726742AbfEIFOP (ORCPT ); Thu, 9 May 2019 01:14:15 -0400 Received: from bootlin.com (lfbn-tou-1-417-253.w86-206.abo.wanadoo.fr [86.206.242.253]) (Authenticated sender: maxime.chevallier@bootlin.com) by relay12.mail.gandi.net (Postfix) with ESMTPSA id 2CD8F200003; Thu, 9 May 2019 05:14:09 +0000 (UTC) Date: Thu, 9 May 2019 07:14:08 +0200 From: Maxime Chevallier To: Jakub Kicinski Cc: davem@davemloft.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Antoine Tenart , thomas.petazzoni@bootlin.com, gregory.clement@bootlin.com, miquel.raynal@bootlin.com, nadavh@marvell.com, stefanc@marvell.com, mw@semihalf.com, Russell King , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH net] net: mvpp2: cls: Add missing NETIF_F_NTUPLE flag Message-ID: <20190509071408.23eae42a@bootlin.com> In-Reply-To: <20190507102803.09fcb56c@cakuba.hsd1.ca.comcast.net> References: <20190507123635.17782-1-maxime.chevallier@bootlin.com> <20190507102803.09fcb56c@cakuba.hsd1.ca.comcast.net> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Jakub, David, On Tue, 7 May 2019 10:28:03 -0700 Jakub Kicinski wrote: >> - if (mvpp22_rss_is_supported()) >> + if (mvpp22_rss_is_supported()) { >> dev->hw_features |= NETIF_F_RXHASH; >> + dev->features |= NETIF_F_NTUPLE; > >Hm, why not in hw_features? Because as of today, there's nothing implemented to disable classification offload in the driver, so the feature can't be toggled. Is this an issue ? Sorry if I'm doing this wrong, but I didn't see any indication that this feature has to be host-writeable. I can make so that it's toggle-able, but it's not as straightforward as we would think, since the classifier is also used for RSS (so, we can't just disable the classifier as a whole, we would have to invalidate each registered flow). Thanks, Maxime