From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: shemminger@vyatta.com, jeff@garzik.org, netdev@vger.kernel.org,
davem@davemloft.net, mpm@selenic.com
Subject: Re: [patch 12/12] Configure out ethtool support
Date: Wed, 30 Jul 2008 14:48:12 -0700 [thread overview]
Message-ID: <20080730144812.a71156f7.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080730233551.76fd38a8@surf>
On Wed, 30 Jul 2008 23:35:51 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Le Wed, 30 Jul 2008 14:01:36 -0700,
> Stephen Hemminger <shemminger@vyatta.com> a __crit :
>
> > Yes, but still concerned that the loss of functionality. The kernel
> > developers have been preaching to get rid of module parameters for
> > configuration, and use a standard interfaces such as ethtool;then the
> > embedded folks want to save a meager 6K.
>
> I understand your point, and I understand that adding many
> configuration options might not look pretty to everybody (even to me).
> However, the kernel developers want to keep embedded people using recent
> versions of the Linux kernel. Unfortunately, the kernel grows release
> after release (see [1] for a report, for example),
There is no [1].
> making the kernel
> less and less usable in certain constrainted embedded contexts where
> older kernels can be used. And people putting Linux in consumer
> electronics devices sold several millions times really do care about
> system size.
>
> The problem is that this kernel growth is well-spread over all the code.
> So yes, it's 6k here, 10k here, 7k there, but once added, it starts to
> be significant.
I note that everybody thinks that their bit cannot possibly be removed,
and that everyone else's can ;)
But I do think we should see some evidence that people are actually
using CONFIG_ETHTOOL=n in real setups.
next prev parent reply other threads:[~2008-07-30 21:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 19:39 [patch 12/12] Configure out ethtool support akpm
2008-07-30 20:37 ` Stephen Hemminger
2008-07-30 20:48 ` Thomas Petazzoni
2008-07-30 21:01 ` Stephen Hemminger
2008-07-30 21:35 ` Thomas Petazzoni
2008-07-30 21:48 ` Andrew Morton [this message]
2008-07-30 21:52 ` Thomas Petazzoni
2008-07-30 22:04 ` Andrew Morton
2008-07-30 23:35 ` Roland Dreier
2008-07-30 21:57 ` David Miller
2008-07-30 22:13 ` Andrew Morton
2008-07-30 22:33 ` David Miller
2008-07-31 10:39 ` David Woodhouse
2008-07-31 10:43 ` David Miller
2008-07-31 10:49 ` David Woodhouse
2008-07-31 10:47 ` David Miller
2008-07-31 15:36 ` Matt Mackall
2008-07-31 15:59 ` Stephen Hemminger
2008-07-31 16:11 ` Matt Mackall
2008-07-31 18:17 ` Evgeniy Polyakov
2008-07-30 21:35 ` David Miller
2008-07-30 21:44 ` Andrew Morton
2008-07-30 22:24 ` Matt Mackall
2008-07-30 22:37 ` David Miller
2008-07-30 23:05 ` Matt Mackall
2008-07-30 23:21 ` David Miller
2008-07-31 1:10 ` Matt Mackall
2008-07-31 1:23 ` David Miller
2008-07-31 10:22 ` Kalle Valo
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=20080730144812.a71156f7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=thomas.petazzoni@free-electrons.com \
/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).