From: Rik van Riel <riel@conectiva.com.br>
To: linux-mm@kvack.org
Subject: Re: Huge vmalloc request? Need help...
Date: Wed, 6 Feb 2002 22:07:23 -0200 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0202062206230.17850-100000@imladris.surriel.com> (raw)
In-Reply-To: <3C617066.3DF01E66@tsl.uu.se>
On Wed, 6 Feb 2002, Yuri Petukhov wrote:
> I tried to allocate (vmalloc) huge (512MB) memory block inside my
> init_module(), but without success. It is possible to get about
> 48MB only. I work on Pentium SMP, 1GB RAM, RedHat-6.2 with kernel
> 2.2.18. Is there some restrictions on vmalloc'ed size? I need
> non-swapped memory block, of course.
Don't do this, you don't need this space.
On a 1 GB machine, the system leaves only 128 MB of space
for both highmem bounce buffers and vmalloc.
Your solution would be to keep track of which pages you're
using yourself.
regards,
Rik
--
"Linux holds advantages over the single-vendor commercial OS"
-- Microsoft's "Competing with Linux" document
http://www.surriel.com/ http://distro.conectiva.com/
--
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-mm.org/
parent reply other threads:[~2002-02-07 0:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <3C617066.3DF01E66@tsl.uu.se>]
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=Pine.LNX.4.33L.0202062206230.17850-100000@imladris.surriel.com \
--to=riel@conectiva.com.br \
--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