From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: lgrijincu@ixiacom.com, netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH] net: shrink net_device by #ifdef-ing protocol-specific members
Date: Mon, 27 Jul 2009 09:27:12 -0700 (PDT) [thread overview]
Message-ID: <20090727.092712.84381944.davem@davemloft.net> (raw)
In-Reply-To: <1248711781.10463.108.camel@Joe-Laptop.home>
From: Joe Perches <joe@perches.com>
Date: Mon, 27 Jul 2009 09:23:01 -0700
> On Mon, 2009-07-27 at 08:26 -0700, David Miller wrote:
>> From: Lucian Adrian Grijincu <lgrijincu@ixiacom.com>
>> Date: Mon, 27 Jul 2009 18:09:08 +0300
>> > Some members of net_device are used only by some protocols.
>> > If those protocols are not compiled (as modules or linked in) they
>> > should not take up space in the structure.
>> This benefits, at best, %0.000000001 of users of the Linux kernel,
>> because every distribution is going to turn on every single option.
>
> I think the cost of maintaining this is small and the
> percentage of users that benefit underestimated.
Prove it.
Prove that it helps enough to maintain this ifdef abortion in our
header files.
It only gives the false sense of satisfation that we're making our
datastructures less bloated. We're not, and in fact they keep getting
larger, and if we add these ifdefs the new excuse for bloat will be
"but it gets compiled out on embedded et al. builds that don't use
this or that feature."
Putting this crap in is just a big smoke screen which gives a
disincentive for making real improvements in this area.
If I thought this was worthwhile I would have done it 10 years ago.
next prev parent reply other threads:[~2009-07-27 16:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 15:09 [PATCH] net: shrink net_device by #ifdef-ing protocol-specific members Lucian Adrian Grijincu
2009-07-27 15:26 ` David Miller
2009-07-27 16:23 ` Joe Perches
2009-07-27 16:27 ` David Miller [this message]
2009-07-27 16:33 ` Joe Perches
2009-07-28 14:43 ` Octavian Purdila
2009-07-28 16:49 ` Joe Perches
2009-07-29 14:20 ` Octavian Purdila
2009-07-28 17:28 ` David Miller
2009-07-29 10:31 ` Octavian Purdila
2009-07-28 6:57 ` Rémi Denis-Courmont
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=20090727.092712.84381944.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=lgrijincu@ixiacom.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).