public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: anton@samba.org, clameter@engr.sgi.com, vamsi.krishnak@gmail.com,
	tony.luck@intel.com, linux-ia64@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Multiple virtual address mapping for the same code on IA-64 linux kernel.
Date: Thu, 18 Aug 2005 15:18:36 -0700	[thread overview]
Message-ID: <4305093C.9040400@mvista.com> (raw)
In-Reply-To: <20050818.142840.82684573.davem@davemloft.net>

David S. Miller wrote:
> From: Anton Blanchard <anton@samba.org>
> Date: Fri, 19 Aug 2005 04:29:55 +1000
> 
> 
>>Calling itanium the "fastest 64bit processor at any given clock frequency"
>>on lkml is likewise inflammatory :)
> 
> 
> I totally agree.

Since the itanium off loads a lot of its instruction steam decisions on 
to the compiler(s), where other processors just do it, one might argue 
that you can not even characterize the itanium without bundling in the 
compilers...

Not to say that is wrong but just to make it clear that saying the 
itanium speed is <X> is like saying that a cummings diesel is fast with 
out saying what sort of car/truck it is mounted in.

-- 
George Anzinger   george@mvista.com
HRT (High-res-timers):  http://sourceforge.net/projects/high-res-timers/

  reply	other threads:[~2005-08-18 22:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 20:44 Multiple virtual address mapping for the same code on IA-64 linux kernel Luck, Tony
2005-08-16 21:27 ` vamsi krishna
2005-08-17 19:52   ` Christoph Lameter
2005-08-18  9:54     ` Alan Cox
2005-08-18 18:29     ` Anton Blanchard
2005-08-18 21:28       ` David S. Miller
2005-08-18 22:18         ` George Anzinger [this message]
2005-08-19 11:00           ` Ingo Oeser
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16 20:36 vamsi krishna
2005-08-16 20:41 ` Andreas Schwab
2005-08-16 21:05 ` linux-os (Dick Johnson)

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=4305093C.9040400@mvista.com \
    --to=george@mvista.com \
    --cc=anton@samba.org \
    --cc=clameter@engr.sgi.com \
    --cc=davem@davemloft.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=vamsi.krishnak@gmail.com \
    /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