From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: vamsi krishna <vamsi.krishnak@gmail.com>,
"Luck, Tony" <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 10:54:38 +0100 [thread overview]
Message-ID: <1124358878.13511.8.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.62.0508171246070.17863@schroedinger.engr.sgi.com>
On Mer, 2005-08-17 at 12:52 -0700, Christoph Lameter wrote:
> > compared to small, this may be the reason why amd64 is the fasttest
> > 64-bit process ?
> Itanium processors are the fastest 64bit processors at any given clock
> frequency.
Perhaps, and the two statements don't contradict. All he was doing was
asking a very sensible architecture question to understand why the IA64
binary was so big.
> Please do not make such inflammatory statements on the
> ia64 list.
Since when has asking sensible questions been "inflammatory statements".
If thats how you treat the people actually porting to IA64 then its out
of order, at least for linux-kernel, which is where you cross posted.
Alan
next prev parent reply other threads:[~2005-08-18 9:27 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 [this message]
2005-08-18 18:29 ` Anton Blanchard
2005-08-18 21:28 ` David S. Miller
2005-08-18 22:18 ` George Anzinger
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=1124358878.13511.8.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=clameter@engr.sgi.com \
--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