From: Andi Kleen <ak@muc.de>
To: Hua Ji <hji@netscreen.com>
Cc: David Pinedo <dp@fc.hp.com>, linux-mm@kvack.org
Subject: Re: Running out of vmalloc space
Date: Thu, 17 May 2001 22:17:02 +0200 [thread overview]
Message-ID: <20010517221702.A1750@fred.local> (raw)
In-Reply-To: <A33AEFDC2EC0D411851900D0B73EBEF766DC67@NAPA>; from hji@netscreen.com on Thu, May 17, 2001 at 08:51:49PM +0200
On Thu, May 17, 2001 at 08:51:49PM +0200, Hua Ji wrote:
> For example, if your machine has a physical memory of 256M. And then your
> vmalloc can only manage
> (1G-256M-8M) space.
Not quite true with 2.4 anymore: Linux can put physical memory that doesn't
fit between PAGE_OFFSET and the beginning of special mappings into highmem,
where it is only mapped from on demand.
Highmem has some penalties (double buffering on IO, cannot be used directly
by many kernel subsystems), but is still usable.
So moderately increasing the vmalloc area should not be a big problem. Of
course it should still leave some directly mapped space for the kernel.
-Andi
--
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 20:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-17 18:51 Hua Ji
2001-05-17 20:17 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 21:58 Hua Ji
2001-05-18 8:21 ` Matti Aarnio
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
2001-05-17 20:10 ` 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=20010517221702.A1750@fred.local \
--to=ak@muc.de \
--cc=dp@fc.hp.com \
--cc=hji@netscreen.com \
--cc=linux-mm@kvack.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