mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M. Edward Borasky" <znmeb@aracnet.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Harald Holzer" <harald.holzer@eunet.at>, <linux-kernel@vger.kernel.org>
Subject: RE: i686 SMP systems with more then 12 GB ram with 2.4.x kernel ?
Date: Tue, 1 Jan 2002 11:02:18 -0800	[thread overview]
Message-ID: <HBEHIIBBKKNOBLMPKCBBMEAKEFAA.znmeb@aracnet.com> (raw)
In-Reply-To: <E16LTvs-00016I-00@the-village.bc.nu>

> > 2. Isn't the boundary at 2^30 really irrelevant and the three "correct"
> > zones are (0 - 2^24-1), (2^24 - 2^32-1) and (2^32 - 2^36-1)?
>
> Nope. The limit for directly mapped memory is 2^30.

Ouch! That makes low memory *extremely* precious. Intuitively, the demand
for directly mapped memory will be proportional to the demand for all
memory, with a proportionality constant depending on the purpose for the
system and the efficiency of the application set. We've seen (apparently --
I haven't looked at any data, just messages on the list) cases where we can
force this to happen with benchmarks designed to embarrass the VM :)) but
have we seen it in real applications?

Thanks for taking the time to answer these questions. I'm struggling to
understand where the performance walls are in large i686 systems, in both
Linux and Windows. In the end, though, relentless application of Moore's Law
to the IA64 must be the correct answer :)).
--
M. Edward Borasky

znmeb@borasky-research.net
http://www.borasky-research.net


  reply	other threads:[~2002-01-01 19:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1009995669.1253.17.camel@wookie-laptop.pdx.osdl.net>
2001-12-29 18:18 ` Harald Holzer
2001-12-29 18:45   ` Alan Cox
2001-12-29 21:24     ` M. Edward (Ed) Borasky
2001-12-30  0:25       ` M. Edward (Ed) Borasky
2001-12-30  2:14         ` Harald Holzer
2001-12-30  2:33           ` M. Edward Borasky
2002-01-01 18:15     ` M. Edward Borasky
2002-01-01 18:46       ` Alan Cox
2002-01-01 19:02         ` M. Edward Borasky [this message]
2002-01-02  1:16         ` H. Peter Anvin
2002-01-02 21:17         ` Gerrit Huizenga
2002-01-06  8:20           ` Benjamin LaHaise
2002-01-06 16:16             ` Alan Cox
2002-01-06 20:23               ` Benjamin LaHaise
2002-01-06 23:37               ` Chris Wedgwood
2002-01-07  0:29                 ` The COUGAR Project M. Edward Borasky
2002-01-07  2:18                 ` i686 SMP systems with more then 12 GB ram with 2.4.x kernel ? Marvin Justice
2002-01-07  2:38                   ` Chris Wedgwood
2002-01-07  4:40                     ` T. A.
2002-01-07 16:20               ` Hugh Dickins
2002-01-02 17:30   ` Timothy D. Witham
     [not found]     ` <1009994687.12942.14.camel@hh2.hhhome.at>
2002-01-02 23:50       ` Harald Holzer
2002-01-03  0:16         ` Alan Cox
2002-01-03 13:30           ` Rik van Riel
2002-01-04 12:09             ` Hugh Dickins
2002-01-04 12:15               ` Rik van Riel
2002-01-03  0:17         ` Mark Zealey
2002-01-03 13:28         ` Rik van Riel
2002-01-03 14:33         ` Stephan von Krawczynski
2002-01-03 16:38           ` Rik van Riel
2002-01-03 15:15         ` Anton Blanchard
2001-12-29 19:25 Dieter Nützel
2002-01-06 18:39 Daniel Freedman
2002-01-06 18:59 ` Marvin Justice
2002-01-06 19:45   ` Daniel Freedman
2002-01-06 20:15     ` Marvin Justice
2002-01-07  5:17       ` Daniel Freedman

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=HBEHIIBBKKNOBLMPKCBBMEAKEFAA.znmeb@aracnet.com \
    --to=znmeb@aracnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=harald.holzer@eunet.at \
    --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

all inboxes | Powered by JetHome®