From: Andi Kleen <ak@suse.de>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities
Date: Tue, 10 Jan 2006 21:55:50 +0100 [thread overview]
Message-ID: <200601102155.51218.ak@suse.de> (raw)
In-Reply-To: <43C417A5.6070104@mnsu.edu>
> Has anyone done any actual benchmark tests that show 64-bit vs 32-bit
> environments/distributions with Athlon64 processors. If so, I love to
> see the results. I too elected to stick with 32-bit, using the same
> reasoning/guessing above.
This discussion is totally off topic on this mailing list. Please stop
it right now. And if not please take me out of cc.
-Andi
next prev parent reply other threads:[~2006-01-10 20:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 20:18 Athlon 64 X2 cpuinfo oddities Jesper Juhl
2006-01-09 20:29 ` Dave Dillow
2006-01-09 22:49 ` Jesper Juhl
2006-01-09 21:10 ` Rafael J. Wysocki
2006-01-09 22:32 ` Edmondo Tommasina
2006-01-09 22:41 ` Jesper Juhl
2006-01-09 22:49 ` Edmondo Tommasina
2006-01-10 1:49 ` Andi Kleen
2006-01-10 2:12 ` Jesper Juhl
2006-01-10 2:36 ` Andi Kleen
2006-01-10 9:29 ` Jesper Juhl
2006-01-10 20:23 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: " Jeffrey Hundstad
2006-01-10 20:34 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfooddities David Lang
2006-01-10 20:50 ` Jeffrey Hundstad
2006-01-10 20:53 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2cpuinfooddities David Lang
2006-01-10 20:55 ` Andi Kleen [this message]
2006-01-11 0:15 ` 64-bit vs 32-bit userspace/kernel benchmark? Was: Athlon 64 X2 cpuinfo oddities Ken Moffat
2006-02-13 2:53 ` Brandon Low
2006-02-13 3:00 ` Alistair John Strachan
2006-02-13 9:20 ` Andi Kleen
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=200601102155.51218.ak@suse.de \
--to=ak@suse.de \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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.