From: "John Stoffel" <john@stoffel.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: John Stoffel <john@stoffel.org>, linux-kernel@vger.kernel.org
Subject: Re: Best CPU chipset for Linux? (was: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19)
Date: Sun, 6 Nov 2005 22:19:50 -0500 [thread overview]
Message-ID: <17262.51158.263211.148554@smtp.charter.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0511061750360.3316@g5.osdl.org>
Linus> On Sun, 6 Nov 2005, John Stoffel wrote:
>>
>> Has any vendor come close to the ideal CPU architecture for an OS? I
>> would assume that you'd want:
Linus> Well, in the end, the #1 requirement ends up being "wide
Linus> availability of development boxes".
Heh! Take my thoughts and turn them on my head. Bravo!
Linus> We do want a "big enough" virtual address space, that's pretty
Linus> much required. It doesn't necessarily have to be the full 64
Linus> bits, and it's fine if the IO space is just a part of that.
So 40 bits is fine for now, but 64 would be great just because it
solves the problem for a long long time?
Linus> As to ISA and registers - nobody much cares. The compiler takes
Linus> care of it, and I'd personally _much_ rather see a common ISA
Linus> than a "clean" one. The x86 architecture may be odd, but it
Linus> works well.
But aren't there areas where the ISA would expose useful parts of the
underlying microarchitecture that could be more efficiently used in
OSes?
Linus> - fast large first-level caches help a lot. And I'd rather
Linus> take a bigger L1 that has a two- or even three-cycle latency
Linus> than a small one. That's assuming the uarch is out-of-order,
Linus> of course.
Linus> - good fast L2, and I'll take low-latency memory access over
Linus> an L3 any day.
Linus> - low-latency serialization (locking and memory barriers). In
Linus> fact, pretty much low-latency everything (branch mispredict
Linus> latency etc).
Linus> - cheap and powerful.
Linus> but the fact is, we'll work with pretty much any crap we're
Linus> given. If it's bad, it won't make it in the marketplace.
The corollary of course is that if it's excellent but the marketplace
doesn't like it for some reason, we'll still let it go. I keep
wishing for the Alpha to come back sometimes... Oh well.
Thanks for your thoughts Linus.
John
next prev parent reply other threads:[~2005-11-07 3:19 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 1:00 [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19 Andy Nelson
2005-11-04 1:16 ` Martin J. Bligh
2005-11-04 1:27 ` Nick Piggin
2005-11-04 5:14 ` Linus Torvalds
2005-11-04 6:10 ` Paul Jackson
2005-11-04 6:38 ` Ingo Molnar
2005-11-04 7:26 ` Paul Jackson
2005-11-04 7:37 ` Ingo Molnar
2005-11-04 15:31 ` Linus Torvalds
2005-11-04 15:39 ` Martin J. Bligh
2005-11-04 15:53 ` Ingo Molnar
2005-11-06 7:34 ` Paul Jackson
2005-11-06 15:55 ` Linus Torvalds
2005-11-06 18:18 ` Paul Jackson
2005-11-06 8:44 ` Kyle Moffett
2005-11-06 16:12 ` Linus Torvalds
2005-11-06 17:00 ` Linus Torvalds
2005-11-07 1:28 ` Best CPU chipset for Linux? (was: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19) John Stoffel
2005-11-07 2:08 ` Linus Torvalds
2005-11-07 3:19 ` John Stoffel [this message]
2005-11-07 8:00 ` [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19 Ingo Molnar
2005-11-07 11:00 ` Dave Hansen
2005-11-07 12:20 ` Ingo Molnar
2005-11-07 19:34 ` Steven Rostedt
2005-11-07 23:38 ` Joel Schopp
2005-11-13 2:30 ` Rob Landley
2005-11-14 1:58 ` Joel Schopp
2005-11-04 7:44 ` Eric Dumazet
2005-11-07 16:42 ` Adam Litke
2005-11-04 14:56 ` Andy Nelson
2005-11-04 15:18 ` Ingo Molnar
2005-11-04 15:39 ` Andy Nelson
2005-11-04 16:05 ` Ingo Molnar
2005-11-04 16:07 ` Linus Torvalds
2005-11-04 16:40 ` Ingo Molnar
2005-11-04 17:22 ` Linus Torvalds
2005-11-04 17:43 ` Andy Nelson
2005-11-04 16:00 ` Linus Torvalds
2005-11-04 16:13 ` Martin J. Bligh
2005-11-04 16:40 ` Linus Torvalds
2005-11-04 17:10 ` Martin J. Bligh
2005-11-04 16:14 ` Andy Nelson
2005-11-04 16:49 ` Linus Torvalds
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=17262.51158.263211.148554@smtp.charter.net \
--to=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome