Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

About limited of process memory!

0 views
Skip to first unread message

Vincent....@gmail.com

unread,
Nov 27, 2008, 8:38:07 PM11/27/08
to
I have a question.
We know that single process can't access more than 3G memory under
linux, is it means that each of parent process and child processes can
access 3G memory?
Or sum of parent process and child processes can only access 3G memory?

Ian Collins

unread,
Nov 28, 2008, 3:50:16 AM11/28/08
to
Vincent....@gmail.com wrote:
> I have a question.
> We know that single process can't access more than 3G memory under
> linux,

Says who?

--
Ian Collins

Vincent....@gmail.com

unread,
Nov 30, 2008, 9:57:25 PM11/30/08
to
On Nov 28, 4:50 pm, Ian Collins <ian-n...@hotmail.com> wrote:

I read it from network and some books, can a single process access
more than 3G memory?

Steve Watt

unread,
Nov 30, 2008, 10:43:38 PM11/30/08
to
In article <6cfb9ac9-14e6-4def...@k1g2000prb.googlegroups.com>,

Vincent....@gmail.com <Vincent....@gmail.com> wrote:
>On Nov 28, 4:50 pm, Ian Collins <ian-n...@hotmail.com> wrote:
>> Vincent.Jiang....@gmail.com wrote:
>> > I have a question.
>> > We know that single process can't access more than 3G memory under
>> > linux,
>>
>> Says who?
>
>I read it from network and some books, can a single process access
>more than 3G memory?

What architecture? Some can, some can't.
--
Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.5" / 37N 20' 15.3"
Internet: steve @ Watt.COM Whois: SW32-ARIN
Free time? There's no such thing. It just comes in varying prices...

Vincent....@gmail.com

unread,
Dec 1, 2008, 1:53:56 AM12/1/08
to

> What architecture?  Some can, some can't.
> --
> Steve Watt KD6GGD  PP-ASEL-IA          ICBM: 121W 56' 57.5" / 37N 20' 15.3"
>  Internet: steve @ Watt.COM                      Whois: SW32-ARIN
>    Free time?  There's no such thing.  It just comes in varying prices...


Redhat enterprise linux4, some of them are32bit, others are 64bit.

Michael Mol

unread,
Dec 1, 2008, 11:39:31 AM12/1/08
to
On Dec 1, 1:53 am, "Vincent.Jiang....@gmail.com"

A 32-bit x86 architecture is limited by a 32-bit address space, which
gives it about 4GB. The OS reserves about 1GB of that. On 64-bit
x86, the address space is 64 bits, which gives you an addressable
range far, far greater than 4GB.

Message has been deleted

Vincent....@gmail.com

unread,
Dec 1, 2008, 7:38:51 PM12/1/08
to
On Dec 2, 1:20 am, Andi Kleen <frei...@alancoxonachip.com> wrote:
> Virtual address space on x86-64 is 48bits, or more accurately 2x47bits
> with a large hole in the middle.  Very few 64bit architectures really
> support true 64bit virtual address space.
>
> Also early x86-64 Linux versions (e.g. RHEL4) limited the
> user addressable part of the address space to 39bits
> (512GB). In later versions it is 47bits for the user space.
>
> -Andi


Thanks a lot.
Can a single Task(Process) access more than 4GB memory on x86-64?

David Schwartz

unread,
Dec 2, 2008, 9:16:40 AM12/2/08
to
On Dec 1, 4:38 pm, "Vincent.Jiang....@gmail.com"

> Thanks a lot.
> Can a single Task(Process) access more than 4GB memory on x86-64?

There is no 4GB limit on x86-64.

DS

0 new messages