From: Ralf Baechle <ralf@conectiva.com.br>
To: "Holzrichter, Bruce" <bruce.holzrichter@monster.com>
Cc: "'Rik van Riel'" <riel@conectiva.com.br>,
Rob Landley <landley@webofficenow.com>,
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: Wed, 13 Jun 2001 12:39:01 +0200 [thread overview]
Message-ID: <20010613123901.A31221@bacchus.dhis.org> (raw)
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6AE1@nocmail.ma.tmpw.net>
In-Reply-To: <3AB544CBBBE7BF428DA7DBEA1B85C79C9B6AE1@nocmail.ma.tmpw.net>; from bruce.holzrichter@monster.com on Tue, Jun 12, 2001 at 02:34:40PM -0400
On Tue, Jun 12, 2001 at 02:34:40PM -0400, Holzrichter, Bruce wrote:
> > Brilliant. You need what, a 6x larger cache just to break even with
> > the amount of time you're running in-cache?
>
> This may be the wrong platform for this question, but after reading Rob
> Landley's note on performance on Itanium and architecture concerns, I am
> interested in Kernel hackers who have had to write code for Itanium's
> comments on the same, if you are not bound by NDA's. Correct me if I am
> wrong, but I thought I saw the announcement that Itanium is shipping. Have
> you tested Itanium performance? We have an preproduction unit with quad
> Itanium's. I have not had time to benchmark against other units, I am
> interested in performance items. Feel free to drop me a line off list if
> you can.
A number of Specbench numbers of Itanium systems is now available. Itanium
performs relativly bad for the integer numbers compared to the entire
competition but is a true fp killer. As a developer I hate that compiling
code for Itanium due to the extra complexity of optimization and code
generation is way slower than for others CPUs. So all in all Itanium is
a two edged sword.
Ralf
next prev parent reply other threads:[~2001-06-13 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 18:34 Any limitations on bigmem usage? Holzrichter, Bruce
2001-06-13 10:39 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=20010613123901.A31221@bacchus.dhis.org \
--to=ralf@conectiva.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bruce.holzrichter@monster.com \
--cc=landley@webofficenow.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnelson@dynatec.com \
--cc=riel@conectiva.com.br \
/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.