From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Olivier Galibert <galibert@limsi.fr>,
Stephan von Krawczynski <skraw@ithnet.com>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com.br>,
neilb@cse.unsw.edu.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: experiences beyond 4 GB RAM with 2.4.22
Date: Wed, 17 Sep 2003 21:19:46 +0200 [thread overview]
Message-ID: <20030917191946.GQ906@suse.de> (raw)
In-Reply-To: <1063811445.12648.69.camel@dhcp23.swansea.linux.org.uk>
On Wed, Sep 17 2003, Alan Cox wrote:
> On Maw, 2003-09-16 at 20:58, Olivier Galibert wrote:
> > On Tue, Sep 16, 2003 at 04:29:02PM +0100, Alan Cox wrote:
> > > The kernel has no idea what you will do with given ram. It does try to
> > > make some guesses but you are basically trying to paper over hardware
> > > limits.
> >
> > Is there a way to specifically turn that ram into a tmpfs though?
>
>
> Something like z2ram copied and hacked a little to kmap the blocks it
> wants would give you a block device you could use for swap or for /tmp.
> Im not sure tmpfs would work here
Aditionally, you need GFP_DMA32 or similar. Would also alleviate the
nasty pressure on ZONE_NORMAL which is often quite stressed.
--
Jens Axboe
next prev parent reply other threads:[~2003-09-17 19:20 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 9:01 experiences beyond 4 GB RAM with 2.4.22 Stephan von Krawczynski
2003-09-09 12:25 ` Andrea Arcangeli
2003-09-12 2:46 ` Neil Brown
2003-09-12 6:54 ` Stephan von Krawczynski
2003-09-12 7:11 ` Jens Axboe
2003-09-12 7:53 ` Mike Fedyk
2003-09-15 22:01 ` Marcelo Tosatti
2003-09-16 8:21 ` Stephan von Krawczynski
2003-09-16 12:05 ` Stephan von Krawczynski
2003-09-16 13:11 ` Marcelo Tosatti
2003-09-16 13:36 ` Stephan von Krawczynski
2003-09-16 13:55 ` Richard B. Johnson
2003-09-16 14:13 ` Stephan von Krawczynski
2003-09-16 14:33 ` Marcelo Tosatti
2003-09-16 14:36 ` Stephan von Krawczynski
2003-09-16 14:36 ` Alan Cox
2003-09-16 15:20 ` Stephan von Krawczynski
2003-09-16 15:29 ` Alan Cox
2003-09-16 15:49 ` Timothy Miller
2003-09-16 16:17 ` Stephan von Krawczynski
2003-09-16 19:58 ` Olivier Galibert
2003-09-17 15:10 ` Alan Cox
2003-09-17 19:19 ` Jens Axboe [this message]
2003-09-17 19:30 ` Marcelo Tosatti
2003-09-17 22:18 ` Stephan von Krawczynski
2003-09-18 7:08 ` Jens Axboe
2003-09-18 7:12 ` Jens Axboe
2003-09-18 11:22 ` Stephan von Krawczynski
2003-09-18 15:05 ` William Lee Irwin III
2003-09-16 17:10 ` Pavel Machek
2003-09-16 19:53 ` Olivier Galibert
2003-09-16 20:04 ` Pavel Machek
2003-09-16 21:16 ` Marcelo Tosatti
2003-09-16 21:23 ` Olivier Galibert
2003-09-17 11:14 ` Stephan von Krawczynski
2003-09-17 13:08 ` Olivier Galibert
2003-09-18 9:58 ` Olivier Galibert
2003-09-18 10:13 ` Stephan von Krawczynski
2003-09-18 11:22 ` Olivier Galibert
2003-09-17 6:41 ` Rogier Wolff
2003-09-17 10:26 ` Jens Axboe
2003-09-17 10:42 ` Rogier Wolff
2003-09-17 10:53 ` Jens Axboe
2003-09-17 19:19 ` Pavel Machek
2003-09-18 11:39 ` Rogier Wolff
2003-09-18 12:13 ` Rogier Wolff
2003-09-16 15:22 ` Timothy Miller
2003-09-16 15:29 ` Martin J. Bligh
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=20030917191946.GQ906@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=galibert@limsi.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com.br \
--cc=neilb@cse.unsw.edu.au \
--cc=skraw@ithnet.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