From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: [bernie@develer.com: Kernel 2.6 size increase]
Date: 23 Jul 2003 23:12:56 GMT [thread overview]
Message-ID: <bfn4po$lu3$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20030723200658.A27856@infradead.org
In article <20030723200658.A27856@infradead.org>,
Christoph Hellwig <hch@infradead.org> wrote:
| 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.
Actually, perhaps some of the non-functional and misfunctional things
might get fixed first and save the diet for 2.6.5 or so. There is no
lack of things which haven't been quiet ported from 2.4, don't work
right, etc.
I doubt that the people who care most about size are going to be doing
a fast change to 2.6 until the dust settles.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-07-23 23:05 UTC|newest]
Thread overview: 7+ 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
2003-07-23 19:09 ` David S. Miller
2003-07-23 19:13 ` Christoph Hellwig
2003-07-23 23:12 ` bill davidsen [this message]
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='bfn4po$lu3$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@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).