[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080730.153340.130551303.davem@davemloft.net>
Date: Wed, 30 Jul 2008 15:33:40 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: akpm@...ux-foundation.org
Cc: thomas.petazzoni@...e-electrons.com, shemminger@...tta.com,
jeff@...zik.org, netdev@...r.kernel.org, mpm@...enic.com
Subject: Re: [patch 12/12] Configure out ethtool support
From: Andrew Morton <akpm@...ux-foundation.org>
Date: Wed, 30 Jul 2008 15:13:16 -0700
> If they don't do this then tens of millions of devices will be burdened
> with many kilobytes of code which they will never ever need.
In the current tree, ethtool is even needed with just the core
IPV4 stack, in order to disable LRO when forwarding is enabled.
See dev_disable_lro() and it's callers in net/ipv4/devinet.c
et al.
As Stephen Hemminger mentioned, bridging uses this too.
So essentially, this new config option would need to depend
on CONFIG_INET, and how useful is that?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists