All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@quark.didntduck.org>
To: devnull@adc.idt.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: >3G Memory support
Date: Wed, 19 Jun 2002 23:29:43 -0400	[thread overview]
Message-ID: <3D114C27.4000801@quark.didntduck.org> (raw)
In-Reply-To: Pine.GSO.4.31.0206191818370.13822-100000@bom.adc.idt.com

devnull@adc.idt.com wrote:
> Hello All.
> 
> I have a PC with 4G of Memory and would like a process to be able to
> address all 4G of memory.
> 
> I am running 2.4.13-ac8
> 
> The way i understand it is that linux shares the top 1G of process address
> space with all processes on the system(so on systems with 4G is physical
> addressability, it leaves 3G for each process).
> 
>>From the archives, i learnt that i need to modify __PAGE_OFFSET and change
> it from the default  (0xC0000000).
> 
> Looking at /usr/src/linux/include/asm-i386/page.h
> 
> <<SNIP>>
> /*
>  * This handles the memory map.. We could make this a config
>  * option, but too many people screw it up, and too few need
>  * it.
>  *
>  * A __PAGE_OFFSET of 0xC0000000 means that the kernel has
>  * a virtual address space of one gigabyte, which limits the
>  * amount of physical memory you can use to about 950MB.
>  *
>  * If you want more physical memory than this then see the
>  *   CONFIG_HIGHMEM4G
>  * and CONFIG_HIGHMEM64G options in the kernel configuration.
>  */
> 
> <<END_OF_SNIP>>
> 
> When i compiled my kernel, i set CONFIG_HIGHMEM4G.
> 
> Does this mean that all my programs should be able to address 4G ?

No.  It means the kernel can access all 4GB of memory.  For memory above 
the 950MB that it can directly map, it needs to use dynamic mappings 
(kmap).  User space is always 3GB virtual space per process, regardless 
of the highmem setting.

--
				Brian Gerst


  reply	other threads:[~2002-06-20  3:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 22:30 >3G Memory support devnull
2002-06-20  3:29 ` Brian Gerst [this message]
2002-06-20 14:18   ` devnull
2002-06-20 14:42     ` Brian Gerst
2002-06-20 14:50       ` Jirka Kosina
2002-06-20 15:27         ` William Lee Irwin III
2002-06-20 15:42     ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20  2:01 marc.miller
2002-06-20  2:08 ` William Lee Irwin III
2002-06-20  4:38   ` Eric W. Biederman

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=3D114C27.4000801@quark.didntduck.org \
    --to=bgerst@quark.didntduck.org \
    --cc=devnull@adc.idt.com \
    --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 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.