From: Ingo Oeser <ioe-lkml@rameria.de>
To: george@mvista.com
Cc: "David S. Miller" <davem@davemloft.net>,
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: Fri, 19 Aug 2005 11:00:52 +0000 [thread overview]
Message-ID: <200508191301.01534.ioe-lkml@rameria.de> (raw)
In-Reply-To: <4305093C.9040400@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 380 bytes --]
Hi,
On Friday 19 August 2005 00:18, George Anzinger wrote:
> 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.
Yes, esp. since we all known that the fastest diesel is actually
Vin Diesel :-)
Have Fun!
Ingo Oeser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-19 11:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 20:48 Multiple virtual address mapping for the same code on IA-64 linux kernel vamsi krishna
2005-08-16 20:41 ` Andreas Schwab
2005-08-16 20:44 ` Luck, Tony
2005-08-16 21:39 ` vamsi krishna
2005-08-17 19:52 ` Multiple virtual address mapping for the same code on IA-64 Christoph Lameter
2005-08-18 9:54 ` Alan Cox
2005-08-18 18:29 ` Multiple virtual address mapping for the same code on IA-64 linux kernel Anton Blanchard
2005-08-18 21:28 ` Multiple virtual address mapping for the same code on IA-64 David S. Miller
2005-08-18 22:18 ` Multiple virtual address mapping for the same code on IA-64 linux George Anzinger
2005-08-19 11:00 ` Ingo Oeser [this message]
2005-08-18 6:55 ` Multiple virtual address mapping for the same code on IA-64 linux kernel vamsi krishna
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=200508191301.01534.ioe-lkml@rameria.de \
--to=ioe-lkml@rameria.de \
--cc=anton@samba.org \
--cc=clameter@engr.sgi.com \
--cc=davem@davemloft.net \
--cc=george@mvista.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