From: Ravi <kravi26@yahoo.com>
To: "Amit S. Jain" <amitjain@tifr.res.in>, linux-mm@kvack.org
Subject: Re: Memory allocation in Linux (fwd)
Date: Thu, 4 Apr 2002 10:38:21 -0800 (PST) [thread overview]
Message-ID: <20020404183821.25904.qmail@web12301.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0204041258240.24668-100000@mailhost.tifr.res.in>
> Obtaining large amount of continuous memory from the kernel is not a
> good practice and is also not possible.However,as far as
> non-contiguous memory is concerned ...cant those be obtained in huge
> amounts (I am talkin in terms of MB).Using get_free_pages or vmalloc
> cant large amounts of memory be obtained.
__get_free_pages() allocates physically contiguous pages, so it
doesn't help you. vmalloc() may be used to get more memory than you
would with kmalloc(), but it isn't guaranteed to succeed. vmalloc can
fail for two reasons (AFAIK):
- vmalloc maps physically discontiguous pages to kernel virtual
addresses in the range of VMALLOC_START and VMALLOC_END. If this
address range is used up, vmalloc will fail.
- allocations done by vmalloc are always backed by physical pages. So
if enough physical memory is not available to satisfy the request,
vmalloc will fail.
Hope this helps,
Ravi.
__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.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/
prev parent reply other threads:[~2002-04-04 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-04 7:34 Amit S. Jain
2002-04-04 11:52 ` Joseph A Knapka
2002-04-11 12:46 ` Amit S. Jain
2002-04-11 22:08 ` Benjamin LaHaise
2002-04-15 8:45 ` Amit S. Jain
2002-04-19 17:46 ` Eric W. Biederman
2002-04-04 18:38 ` Ravi [this message]
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=20020404183821.25904.qmail@web12301.mail.yahoo.com \
--to=kravi26@yahoo.com \
--cc=amitjain@tifr.res.in \
--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