public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian Gerst <bgerst@didntduck.org>
To: devnull@adc.idt.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: >3G Memory support
Date: Thu, 20 Jun 2002 10:42:53 -0400	[thread overview]
Message-ID: <3D11E9ED.7060101@didntduck.org> (raw)
In-Reply-To: Pine.GSO.4.31.0206201010340.13158-100000@bom.adc.idt.com

devnull@adc.idt.com wrote:
>>>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.
> 
> 
> Is there a way to make a process in the user space to able to access 4GB
> at all. 

Not all at one time, but you can map/unmap shared memory segments to 
access more memory.

> What limits user space to 3GB.

Hardware limitations imposed by the x86 architecture.  The x86 only has 
_one_ virtual address space, which has to be shared by user space and 
kernel space.  It is not possible to give user space more virtual 
address space without taking it away from the kernel.

> If not in current 2.4.x / 2.5.x, is this something planned in the future
> releases ?

Support for 64-bit processors like Intel Itanium and AMD Hammer 
processors which do not have such limitations.

--
				Brian Gerst


  reply	other threads:[~2002-06-20 14:43 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
2002-06-20 14:18   ` devnull
2002-06-20 14:42     ` Brian Gerst [this message]
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=3D11E9ED.7060101@didntduck.org \
    --to=bgerst@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox