All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-mm@kvack.org
Subject: Re: Big memory, no struct page allocation
Date: Sun, 23 Jun 2002 23:31:28 +0800	[thread overview]
Message-ID: <3D15E9D0.1090209@shaolinmicro.com> (raw)
In-Reply-To: 20020623085914.GN25360@holomorphy.com

William Lee Irwin III wrote:

>On Sun, Jun 23, 2002 at 04:55:58PM +0800, David Chow wrote:
>  
>
>>Hi, I've got a silly but serious question. I want to allocate a large 
>>buffer (>512MB) in kernel. Normally you use __get_free_page and handle 
>>it with page pointers. But when get to very large (say 1024MB), I will 
>>need to use 2 level of page pointer indirection to carry the page 
>>pointer array. I also find the total size of page struct is quite large 
>>when using lots of pages, what I want is to use memory pages without 
>>struct page, is this possible? By the way, can I use lots of memory in 
>>the kernel, something like 1GB of memory allocation when physically RAM 
>>available? Please give advise. Thanks.
>>    
>>
>
>Try allocating it at boot-time with the bootmem allocator.
>
>
>Cheers,
>Bill
>  
>
Thanks for suggestions, you mean this will allow no struct page or can 
use memory more than 1GB? Please make clear on direction, I would love 
to know. Thanks.

regards,
David


--
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/

  reply	other threads:[~2002-06-23 15:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-23  8:55 Big memory, no struct page allocation David Chow
2002-06-23  8:59 ` William Lee Irwin III
2002-06-23 15:31   ` David Chow [this message]
2002-06-27  1:38     ` William Lee Irwin III
2002-06-30 18:38       ` David Chow
2002-07-01 17:48         ` Rik van Riel
2002-07-02  6:06           ` William Lee Irwin III
2002-07-03 16:16             ` David Chow

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=3D15E9D0.1090209@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.