From: Mike Touloumtzis <miket@bluemug.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Acpi] Re: ACPI fundamental locking problems
Date: Sat, 7 Jul 2001 15:04:22 -0700 [thread overview]
Message-ID: <20010707150422.D19529@mayotte> (raw)
In-Reply-To: <Pine.LNX.4.33.0107040956310.1668-100000@penguin.transmeta.com> <9i6oga$jk1$1@pccross.average.org> <3B46F3CE.9002ABAB@mandrakesoft.com> <20010707144032.C19529@mayotte> <20010707235329.A10256@pcep-jamie.cern.ch>
In-Reply-To: <20010707235329.A10256@pcep-jamie.cern.ch>
On Sat, Jul 07, 2001 at 11:53:29PM +0200, Jamie Lokier wrote:
> Mike Touloumtzis wrote:
> >
> > Would it be possible to use a cramfs image in vmlinux (i.e. real
> > filesystem image, not an in-kernel-structures fs like ramfs), and map
> > it directly from the kernel image (it would have to be suitably aligned,
> > of course)?
> >
> > This would allow demand paging of files in the image (not too important
> > for a minimal boot fs, admittedly), and would allow text pages to be
> > dropped under VM pressure (nice for a fs which holds substantial amounts
> > of boot-time-only code).
>
> Yes that would work, and it would work on machines with less RAM too.
> You would want to remove the cramfs filesystem code when you're done though.
Some of the files in the boot time FS would need to
be kept around, such as the ACPI code, right?
miket
next prev parent reply other threads:[~2001-07-07 22:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 10:37 [Acpi] Re: ACPI fundamental locking problems Dave J Woolley
2001-07-04 11:03 ` Alan Cox
2001-07-04 17:05 ` Linus Torvalds
2001-07-05 8:20 ` Helge Hafting
2001-07-05 8:34 ` Jeff Garzik
2001-07-05 11:21 ` Alan Cox
2001-07-05 13:42 ` Alexander Viro
2001-07-05 15:17 ` Linus Torvalds
2001-07-06 7:34 ` Benjamin Herrenschmidt
2001-07-06 8:45 ` Helge Hafting
2001-07-06 11:16 ` Alan Cox
2001-07-06 12:42 ` Daniel Phillips
2001-07-09 23:05 ` Pavel Machek
2001-07-07 10:32 ` Eugene Crosser
2001-07-07 11:32 ` Alexander Viro
2001-07-07 13:37 ` Eugene Crosser
2001-07-07 13:50 ` Jeff Garzik
2001-07-07 17:24 ` Daniel Phillips
2001-07-07 21:31 ` Jamie Lokier
2001-07-07 21:44 ` Steve VanDevender
2001-07-08 7:26 ` Alexander Viro
2001-07-08 16:46 ` Jonathan Lundell
2001-07-09 14:40 ` Anthony DeBoer
2001-07-07 11:34 ` Jeff Garzik
2001-07-07 21:40 ` Mike Touloumtzis
2001-07-07 21:54 ` Jamie Lokier
2001-07-07 22:00 ` arjan
2001-07-07 22:15 ` Jamie Lokier
2001-07-07 22:04 ` Mike Touloumtzis [this message]
2001-07-07 22:14 ` Jamie Lokier
2001-07-08 2:57 ` Keith Owens
2001-07-12 15:57 ` Eric W. Biederman
2001-07-12 16:14 ` Jeff Garzik
2001-07-12 21:18 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2001-07-06 5:26 Andreas Dilger
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=20010707150422.D19529@mayotte \
--to=miket@bluemug.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
/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