From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Aaron Lehmann <aaronl@vitelus.com>,
Linus Torvalds <torvalds@transmeta.com>,
LKML <linux-kernel@vger.kernel.org>,
viro@math.psu.edu
Subject: Re: [BK PATCHES] initramfs merge, part 1 of N
Date: Sat, 02 Nov 2002 00:50:27 -0800 [thread overview]
Message-ID: <3DC391D3.7040005@zytor.com> (raw)
In-Reply-To: 3DC390F2.6040600@pobox.com
Jeff Garzik wrote:
> Aaron Lehmann wrote:
>
>> On Sat, Nov 02, 2002 at 03:13:45AM -0500, Jeff Garzik wrote:
>>
>>
>>> The Future.
>>>
>>> Early userspace is going to be merged in a series of evolutionary
>>> changes, following what I call "The Al Viro model." NO KERNEL
>>> BEHAVIOR SHOULD CHANGE. [that's for the lkml listeners, not you
>>> <g>] "make" will continue to simply Do The Right Thing(tm) on all
>>> platforms, while the kernel image continues to get progressively
>>> smaller.
>>>
>>
>>
>> Won't the initial userspace be linked into the kernel? If so, why will
>> the kernel image get smaller?
>>
>>
>
> Yes and no ;-)
>
> Ignoring for a moment initramfses loaded from your bootloader (a la
> initrd)... The amount of code that runs in kernel space shrinks, which
> is the main point of early userspace. If you are talking in terms of
> overall kernel image size, yes, but the initramfs cpio archive is
> ditching along with the rest of __init code, so you're really only
> talking about wasting a couple of additional pages in vmlinux -- a
> slight increase in disk space usage, and that's it.
>
> So runtime memory usage certainly does not increase...
>
By the way, the final initramfs should typically be a union of whatever
sources there are; with the ones linked into the kernel image unpacked
first (so they can be overwritten if so specified to the bootloader.)
-hpa
next prev parent reply other threads:[~2002-11-02 8:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 8:13 [BK PATCHES] initramfs merge, part 1 of N Jeff Garzik
2002-11-02 8:18 ` Jeff Garzik
2002-11-02 8:42 ` Aaron Lehmann
2002-11-02 8:46 ` Jeff Garzik
2002-11-02 8:50 ` H. Peter Anvin [this message]
2002-11-02 19:01 ` Linus Torvalds
2002-11-02 12:07 ` H. Peter Anvin
2002-11-02 20:24 ` Alexander Viro
2002-11-02 23:46 ` Dave Cinege
2002-11-02 10:51 ` miltonm
2002-11-02 17:12 ` Matt Porter
2002-11-02 12:14 ` H. Peter Anvin
2002-11-02 20:37 ` an idling kernel Anu
2002-11-02 22:16 ` Jos Hulzink
2002-11-03 0:43 ` identifying the idling kernel and kernel hacking Anu
2002-11-04 19:16 ` an idling kernel Werner Almesberger
2002-11-02 20:37 ` [BK PATCHES] initramfs merge, part 1 of N Alexander Viro
2002-11-02 23:36 ` Matt Porter
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=3DC391D3.7040005@zytor.com \
--to=hpa@zytor.com \
--cc=aaronl@vitelus.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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