linux-mm.kvack.org archive mirror
 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: Mon, 01 Jul 2002 02:38:44 +0800	[thread overview]
Message-ID: <3D1F5034.9060409@shaolinmicro.com> (raw)
In-Reply-To: <20020627013833.GO25360@holomorphy.com>

William Lee Irwin III wrote:

>William Lee Irwin III wrote:
>  
>
>>>Try allocating it at boot-time with the bootmem allocator.
>>>      
>>>
>
>On Sun, Jun 23, 2002 at 11:31:28PM +0800, David Chow wrote:
>  
>
>>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.
>>    
>>
>
>On 32-bit machines with 3:1 process address space splits yes.
>
>In this case you're far better off playing games with the highmem
>initialization in order to slice the memory out of there and kmap it.
>
>
>Cheers,
>Bill
>  
>
In other words, even I have 2G physical memory, I cannot have benefits 
of using all memory for pagecache, this also means I cannot create any 
cache beyong a 1G size in kernel. That's a pitty for 32-bit systems, 
with himem, how does it work?

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-30 18:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-23  8:55 David Chow
2002-06-23  8:59 ` William Lee Irwin III
2002-06-23 15:31   ` David Chow
2002-06-27  1:38     ` William Lee Irwin III
2002-06-30 18:38       ` David Chow [this message]
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=3D1F5034.9060409@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox