From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [bernie@develer.com: Kernel 2.6 size increase]
Date: Wed, 23 Jul 2003 20:06:58 +0100 [thread overview]
Message-ID: <20030723200658.A27856@infradead.org> (raw)
In-Reply-To: <20030723115858.7506829I4.davem@redhat.com>; from davem@redhat.com on Wed, Jul 23, 2003 at 11:58:58AM -0700
On Wed, Jul 23, 2003 at 11:58:58AM -0700, David S. Miller wrote:
> > Sorry, this actually already Cc'ed lkml :) Still the netdev folks
> > should read it, too.
>
> Well, we gained some code and a little bit of data, but
> the BSS was cut in half which I think deserves noticing :-)
>
> Also, he should analyze the amount of code that actually
> gets executed for various tasks, comparing 2.4.x to 2.5.x
>
> I'd take a half-meg code size hit if it meant that all
> the normal code paths got cut in half :-)
half a megabyte more codesize is a lot if you're based on flash.
I know you absolutely disliked Andi's patch to make the xfrm subsystem
optional so we might need find other ways to make the code smaller
on those systems that need it. Now I could talk a lot but I'm really
no networking insider so it's hard for me to suggest where to start.
I'll rather look at the fs/ issue but it would be nice if networking
folks could do their part, too.
next prev parent reply other threads:[~2003-07-23 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 18:53 [bernie@develer.com: Kernel 2.6 size increase] Christoph Hellwig
2003-07-23 18:55 ` Christoph Hellwig
2003-07-23 18:58 ` David S. Miller
[not found] ` <20030723115858.7506829I4.davem@redhat.com>
2003-07-23 19:06 ` Christoph Hellwig [this message]
2003-07-23 19:09 ` David S. Miller
2003-07-23 19:13 ` Christoph Hellwig
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=20030723200658.A27856@infradead.org \
--to=hch@infradead.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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).