From: Christoph Hellwig <hch@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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:13:35 +0100 [thread overview]
Message-ID: <20030723201335.A27990@infradead.org> (raw)
In-Reply-To: <20030723120901.57746fd8.davem@redhat.com>; from davem@redhat.com on Wed, Jul 23, 2003 at 12:09:01PM -0700
On Wed, Jul 23, 2003 at 12:09:01PM -0700, David S. Miller wrote:
> So basically we'd have a CONFIG_NET_XFRM, and things like
> AH/ESP/IPCOMP/AH6/ESP6/IPCOMP6 would say "select NET_XFRM"
> in the Kconfig where they are selected.
>
> Then when CONFIG_NET_XFRM is not set all the xfrm interfaces
> called from non-ipsec non-xfrm source files get NOP versions.
>
> Is this exactly what Andi's patch did? Just send it on
> so we can integrate this.
I think that's what it did modula the select which IIRC wasn't
available back then. But I guess I'll rather leave this to
Andi.
> We actually lost a lot of code in other areas of the networking, for
> example Andrew Morton and I made many bogus function inlines
> undone because they made the code too large.
That's cool! Now we just need to find a bunch more regressions
and actually make 2.6 smaller than 2.4 :) Of course that's true
for the other subsystems, too.
next prev parent reply other threads:[~2003-07-23 19:01 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 [this message]
2003-07-23 23:12 ` bill davidsen
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=20030723201335.A27990@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.