From: ebiederm@xmission.com (Eric W. Biederman)
To: afei@jhu.edu
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Joseph A Knapka <jknapka@earthlink.net>,
"Gabriel.Leen" <Gabriel.Leen@ul.ie>,
"'linux-mm@kvack.org'" <linux-mm@kvack.org>
Subject: Re: Process not given >890MB on a 4MB machine ?????????
Date: 26 Sep 2001 01:04:00 -0600 [thread overview]
Message-ID: <m1n13i5t7j.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.GSO.4.05.10109251335380.23459-100000@aa.eps.jhu.edu>
afei@jhu.edu writes:
> The current Linux MM design is a 3:1 split of 4G virtual/physical memory.
> So a process, under normal condition cannot get beyond 3G memory
> allocated.
The current Linux i386 MM usage is a 3:1 split of 4G virtual
memory. 3GB for the uesr process. 1GB for the kernel. With all of
the highmem tricks the kernel can access up to 16TB of physical memory
on a 32 bit system but the i386 architeture only provides for a
maximum of 64GB of physical memory.
A user space process is free to implement it's own paging of a file or
a shared memory region in and out of it's address space but that
usually requires code redesign, so few people go for it.
Eric
--
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/
next prev parent reply other threads:[~2001-09-26 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 22:41 Gabriel.Leen
2001-09-24 21:16 ` Joseph A Knapka
2001-09-25 10:59 ` Stephen C. Tweedie
2001-09-25 17:36 ` afei
2001-09-26 7:04 ` Eric W. Biederman [this message]
2001-09-26 8:53 ` Stephen C. Tweedie
[not found] <5D2F375D116BD111844C00609763076E050D1681@exch-staff1.ul.ie>
2001-09-24 22:49 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2001-09-24 21:15 Gabriel.Leen
2001-09-24 22:16 ` Jonathan Morton
2001-09-21 16:07 Gabriel.Leen
2001-09-22 2:01 ` Rik van Riel
2001-09-20 19:25 Gabriel.Leen
2001-09-20 19:56 ` brian
2001-09-20 20:36 ` Thierry Vignaud
2001-09-20 20:56 ` Benjamin LaHaise
2001-09-21 8:29 ` 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=m1n13i5t7j.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=Gabriel.Leen@ul.ie \
--cc=afei@jhu.edu \
--cc=jknapka@earthlink.net \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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