git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Francis Moreau <francis.moro@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH 0/17] Sliding window mmap for packfiles.
Date: Sun, 24 Dec 2006 01:29:29 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612240126380.3671@woody.osdl.org> (raw)
In-Reply-To: <38b2ab8a0612240056k152344ael891e9b0b9f8cbc47@mail.gmail.com>



On Sun, 24 Dec 2006, Francis Moreau wrote:
> 
> Just out of curiosity, do you mean that there are some OS running on
> 32 bits machines which allow 4GiB size of virtual memory within a
> single process ? If so, could you give an example of such OS ?

Actually, Linux will do it on certain architectures (some architectures 
have separate "address spaces" for kernel and user). And even on x86, if 
you apply the (insane) 4GB patches, user space will actually have almost 
all of the 4GB, because there's only a _tiny_ trampoline thing that 
switches the whole page table around that is kernel-mapped and takes away 
from the 4GB thing.

In practice, though, most 32-bit architectures will have between 1-3GB of 
user virtual memory. And obviously stack space, binaries, heap etc take up 
space, so you often end up with with just ~0.5 GB of actual dependable 
contiguous virtual memory.

			Linus

      parent reply	other threads:[~2006-12-24  9:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-23  7:33 [PATCH 0/17] Sliding window mmap for packfiles Shawn O. Pearce
2006-12-23  9:37 ` Junio C Hamano
2006-12-23  9:42   ` Shawn Pearce
2006-12-24  8:56 ` Francis Moreau
2006-12-24  9:05   ` Shawn Pearce
2006-12-24  9:36     ` Francis Moreau
2006-12-24  9:49       ` Shawn Pearce
2007-01-02 15:28         ` Andy Whitcroft
2006-12-24  9:29   ` Linus Torvalds [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0612240126380.3671@woody.osdl.org \
    --to=torvalds@osdl.org \
    --cc=francis.moro@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).