linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Rob Landley <landley@webofficenow.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Matt Nelson <mnelson@dynatec.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Any limitations on bigmem usage?
Date: Tue, 12 Jun 2001 15:16:46 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0106121514300.14934-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <01061208465701.00814@webofficenow.com>

On Tue, 12 Jun 2001, Rob Landley wrote:

> Brilliant.  You need what, a 6x larger cache just to break even with
> the amount of time you're running in-cache? 

That's going to be hard, since the cache will also need to be
faster in order to feed the CPU core.  Making a cache both
larger AND faster at the same time will need some smart people.

> And of course the compiler is GOING to put NOPs in that because it
> won't always be able to figure out something for the second and third
> cores to do this clock, regardless of how good a compiler it is.  

Compilers are also notoriously bad at runtime optimisations.

> That's just beautiful.

I also never expected Intel to dispose of themselves in such
a cute way.

cheers,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/		http://distro.conectiva.com/

Send all your spam to aardvark@nl.linux.org (spam digging piggy)


  reply	other threads:[~2001-06-12 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12  0:18 Matt Nelson
2001-06-12  0:31 ` Doug McNaught
2001-06-12  0:38   ` Doug McNaught
2001-06-12 14:03 ` Matt Nelson
2001-06-12 16:29 ` Alan Cox
2001-06-12 12:46   ` Rob Landley
2001-06-12 18:16     ` Rik van Riel [this message]
2001-06-12 18:34 Holzrichter, Bruce
2001-06-13 10:39 ` Ralf Baechle

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=Pine.LNX.4.21.0106121514300.14934-100000@imladris.rielhome.conectiva \
    --to=riel@conectiva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=landley@webofficenow.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnelson@dynatec.com \
    --subject='Re: Any limitations on bigmem usage?' \
    /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

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 NNTP newsgroup(s).