From: Timur Tabi <ttabi@interactivesi.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Newbies Mailing List <kernelnewbies@nl.linux.org>
Subject: Allocating more than 890MB in the kernel?
Date: Fri, 19 Oct 2001 13:48:38 -0500 [thread overview]
Message-ID: <3BD07586.3090706@interactivesi.com> (raw)
vmalloc() fails after about 890MB because the kernel memory map is only for
about 1GB. I know there are some hacks and work-arounds to get more than
that, but instead of reinventing the wheel, I was hoping some kind soul would
tell me how (a few hints would be nice!)
The reason we use vmalloc() is because we need to apply memory pressure during
the allocating: memory should be swapped out to make room for our allocation.
We're trying to allocate up to 3GB on a 4GB machine. Thanks in advance!
next reply other threads:[~2001-10-19 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 18:48 Timur Tabi [this message]
2001-10-19 19:04 ` Allocating more than 890MB in the kernel? John Tyner
2001-10-19 19:41 ` Timur Tabi
2001-10-19 19:59 ` H. Peter Anvin
2001-10-19 20:21 ` Timur Tabi
2001-10-19 20:32 ` H. Peter Anvin
2001-10-20 4:40 ` Rob Landley
2001-10-20 18:09 ` H. Peter Anvin
2001-10-25 4:04 ` Albert D. Cahalan
2001-10-26 16:13 ` Timur Tabi
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=3BD07586.3090706@interactivesi.com \
--to=ttabi@interactivesi.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.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