From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: mmap'ing a large file
Date: 15 Aug 2002 12:34:32 -0700 [thread overview]
Message-ID: <ajgvo8$qh6$1@cesium.transmeta.com> (raw)
In-Reply-To: 1029342745.8255.6.camel@lemsip
Followup to: <1029342745.8255.6.camel@lemsip>
By author: Gianni Tedesco <gianni@ecsc.co.uk>
In newsgroup: linux.dev.kernel
>
> Intel is a 32bit architecture, that is to say the address space is 2^32
> bytes (4GB), of this address space the kernel takes the top 2GB and
> userspace the bottom 2GB.
>
NAK. 3 GB userspace, 1 GB kernel space is the default.
The 3 GB is subdivided into 1 GB for the program, and 2 GB for libraries
and other mmaps (grows up) and the stack (grows down).
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-08-15 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 15:42 mmap'ing a large file Mike Black
2002-08-14 16:32 ` Gianni Tedesco
2002-08-14 19:42 ` Jamie Lokier
2002-08-15 19:34 ` H. Peter Anvin [this message]
2002-08-15 10:02 ` DervishD
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='ajgvo8$qh6$1@cesium.transmeta.com' \
--to=hpa@zytor.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