From: Christoph Hellwig <hch@caldera.de>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: David Pinedo <dp@fc.hp.com>, linux-mm@kvack.org
Subject: Re: Running out of vmalloc space
Date: Thu, 17 May 2001 21:23:10 +0200 [thread overview]
Message-ID: <20010517212310.A5122@caldera.de> (raw)
In-Reply-To: <20010517221610.K5947@mea-ext.zmailer.org>; from matti.aarnio@zmailer.org on Thu, May 17, 2001 at 10:16:10PM +0300
On Thu, May 17, 2001 at 10:16:10PM +0300, Matti Aarnio wrote:
> On Thu, May 17, 2001 at 11:13:00AM -0600, David Pinedo wrote:
> [ Why vmalloc() space is so small ? ]
>
> Hua Ji summarized quite well what the kernel does, and where.
>
> There are 32bit machines which *can* access whole 4G kernel space
> separate from simultaneous 4G user space, however i386 is not one
> of those.
Kanoj Sarcar has written a patch for Linux 2.2 to allow exactly this.
Take a look at http://oss.sgi.com/projects/bigmem/, the page also
contains a nice explanation of what the changes actually do.
Christoph
--
Whip me. Beat me. Make me maintain AIX.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-05-17 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 17:13 David Pinedo
2001-05-17 17:39 ` Stephen C. Tweedie
2001-05-17 22:48 ` David Pinedo
2001-05-18 11:24 ` Andi Kleen
2001-05-18 11:53 ` Stephen C. Tweedie
2001-05-18 16:44 ` Christoph Hellwig
2001-05-22 23:15 ` David Pinedo
2001-05-23 9:35 ` Stephen C. Tweedie
2001-05-23 16:14 ` David Pinedo
2001-05-23 16:45 ` Stephen C. Tweedie
2001-05-26 5:13 ` Andrew Morton
2001-05-17 19:16 ` Matti Aarnio
2001-05-17 19:23 ` Christoph Hellwig [this message]
2001-05-17 20:10 ` Matti Aarnio
2001-05-17 18:51 Hua Ji
2001-05-17 20:17 ` Andi Kleen
2001-05-17 21:58 Hua Ji
2001-05-18 8:21 ` Matti Aarnio
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=20010517212310.A5122@caldera.de \
--to=hch@caldera.de \
--cc=dp@fc.hp.com \
--cc=linux-mm@kvack.org \
--cc=matti.aarnio@zmailer.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