netdev
[Top] [All Lists]

Re: [NET]: TSO requires SG, enforce this at device registry.

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [NET]: TSO requires SG, enforce this at device registry.
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Mon, 25 Oct 2004 01:50:41 -0400
Cc: Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Netdev <netdev@xxxxxxxxxxx>
In-reply-to: <200410221715.i9MHFlIu021927@xxxxxxxxxxxxxxx>
References: <200410221715.i9MHFlIu021927@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922
Linux Kernel Mailing List wrote:
diff -Nru a/net/core/dev.c b/net/core/dev.c
--- a/net/core/dev.c    2004-10-22 10:15:57 -07:00
+++ b/net/core/dev.c    2004-10-22 10:15:57 -07:00
@@ -2871,6 +2871,14 @@
                dev->features &= ~NETIF_F_SG;
        }
+ /* TSO requires that SG is present as well. */
+       if ((dev->features & NETIF_F_TSO) &&
+           !(dev->features & NETIF_F_SG)) {
+               printk("%s: Dropping NETIF_F_TSO since no SG feature.\n",
+                      dev->name);
+               dev->features &= ~NETIF_F_TSO;
+       }


Although this patch is correct, I am pondering whether this fully covers the problems in the field.

There are currently two classes of problems I am seeing, that generate real-life bug reports:

1) Given current driver implementations of ethtool ioctls, sysadmin is free to create a combination of bits that are IMHO a bug. One can argue that this is an extension of "root can shoot himself in the foot", so who knows.

2) Programmers writing drivers do not appear to be clear that SG is required to tx-csum/tso, and also, should not be present without one or both of those bits set.

        Jeff


<Prev in Thread] Current Thread [Next in Thread>