All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to use memory over 4GB
Date: Mon, 16 May 2005 22:34:00 +0100	[thread overview]
Message-ID: <87hdh2am9j.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <6.2.1.2.2.20050516164236.05922a30@mail.tekno-soft.it> (Roberto Fichera's message of "16 May 2005 15:54:37 +0100")

On 16 May 2005, Roberto Fichera whispered secretively:
> At 16.17 16/05/2005, Eric Dumazet wrote:
>>If your process is cpu bounded (and not issuing too many system calls),
>> then 4GB/4GB split let it address more ram, reducing the need to shift windows in
>>mmaped files for example.
> 
> ... any source code that explain better what you say ;-)!

<http://lkml.org/lkml/2003/7/8/246> perhaps?

(In a nutshell: it gives processes an extra 1Gb of virtual memory, at
the cost of making system calls --- and everything else that must
transition to kernel space --- *much* slower.)

  reply	other threads:[~2005-05-16 21:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 12:42 How to use memory over 4GB Roberto Fichera
2005-05-16 12:56 ` Michael Tokarev
2005-05-16 13:16   ` Roberto Fichera
2005-05-16 15:10     ` William Lee Irwin III
2005-05-16 15:47       ` Roberto Fichera
2005-05-16 15:54         ` William Lee Irwin III
2005-05-16 16:37           ` Roberto Fichera
2005-05-16 19:14   ` Bill Davidsen
2005-05-16 12:57 ` Eric Dumazet
2005-05-16 13:18   ` Roberto Fichera
2005-05-16 14:17     ` Eric Dumazet
2005-05-16 14:50       ` Roberto Fichera
2005-05-16 21:34         ` Nix [this message]
2005-05-17  7:15           ` Roberto Fichera
2005-05-16 15:22       ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 12:55 li nux
2005-05-16 13:06 ` Roberto Fichera

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=87hdh2am9j.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=dada1@cosmosbay.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.