netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Chan <michael.chan@broadcom.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, andrew.gospodarek@broadcom.com,
	Ariel Elior <Ariel.Elior@cavium.com>,
	everest-linux-l2@cavium.com
Subject: [PATCH net-next v2 2/5] net: Disable GRO_HW when generic XDP is installed on a device.
Date: Thu,  7 Dec 2017 03:03:32 -0500	[thread overview]
Message-ID: <1512633815-25037-3-git-send-email-michael.chan@broadcom.com> (raw)
In-Reply-To: <1512633815-25037-1-git-send-email-michael.chan@broadcom.com>

Hardware should not aggregate any packets when generic XDP is installed.

Cc: Ariel Elior <Ariel.Elior@cavium.com>
Cc: everest-linux-l2@cavium.com
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
---
 net/core/dev.c | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)

diff --git a/net/core/dev.c b/net/core/dev.c
index 7242e5e..7087f34 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -1542,6 +1542,29 @@ void dev_disable_lro(struct net_device *dev)
 }
 EXPORT_SYMBOL(dev_disable_lro);
 
+/**
+ *	dev_disable_gro_hw - disable HW Generic Receive Offload on a device
+ *	@dev: device
+ *
+ *	Disable HW Generic Receive Offload (GRO_HW) on a net device.  Must be
+ *	called under RTNL.  This is needed if Generic XDP is installed on
+ *	the device.
+ */
+static void dev_disable_gro_hw(struct net_device *dev)
+{
+	struct net_device *lower_dev;
+	struct list_head *iter;
+
+	dev->wanted_features &= ~NETIF_F_GRO_HW;
+	netdev_update_features(dev);
+
+	if (unlikely(dev->features & NETIF_F_GRO_HW))
+		netdev_WARN(dev, "failed to disable GRO_HW!\n");
+
+	netdev_for_each_lower_dev(dev, lower_dev, iter)
+		dev_disable_gro_hw(lower_dev);
+}
+
 static int call_netdevice_notifier(struct notifier_block *nb, unsigned long val,
 				   struct net_device *dev)
 {
@@ -4545,6 +4568,7 @@ static int generic_xdp_install(struct net_device *dev, struct netdev_bpf *xdp)
 		} else if (new && !old) {
 			static_key_slow_inc(&generic_xdp_needed);
 			dev_disable_lro(dev);
+			dev_disable_gro_hw(dev);
 		}
 		break;
 
-- 
1.8.3.1

  parent reply	other threads:[~2017-12-07  8:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07  8:03 [PATCH net-next v2 0/5] Introduce NETIF_F_GRO_HW Michael Chan
2017-12-07  8:03 ` [PATCH net-next v2 1/5] net: " Michael Chan
2017-12-07 18:13   ` Alexander Duyck
2017-12-07 18:44     ` Michael Chan
2017-12-07 21:35       ` Alexander Duyck
2017-12-07 22:08         ` Michael Chan
2017-12-07 22:43           ` Alexander Duyck
2017-12-07 23:17             ` Michael Chan
2017-12-07 23:35               ` Alexander Duyck
2017-12-08  0:05                 ` Michael Chan
2017-12-08  2:36                   ` Alexander Duyck
2017-12-08  4:02                     ` Michael Chan
2017-12-07  8:03 ` Michael Chan [this message]
2017-12-07  8:03 ` [PATCH net-next v2 3/5] bnxt_en: Use NETIF_F_GRO_HW Michael Chan
2017-12-07  8:03 ` [PATCH net-next v2 4/5] bnx2x: " Michael Chan
2017-12-07  8:03 ` [PATCH net-next v2 5/5] qede: " Michael Chan
2017-12-08 17:02   ` Chopra, Manish
2017-12-08 22:09   ` Marcelo Ricardo Leitner
2017-12-08 22:40     ` Michael Chan

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=1512633815-25037-3-git-send-email-michael.chan@broadcom.com \
    --to=michael.chan@broadcom.com \
    --cc=Ariel.Elior@cavium.com \
    --cc=andrew.gospodarek@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=everest-linux-l2@cavium.com \
    --cc=netdev@vger.kernel.org \
    /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).