DOS was a reverse engineered clone of CP/M with some unix features bolted on
in the early 80's. Dos couldn't multitask on a single CPU. Dos couldn't
handle more than one video card. DOS could barely keep track of more than
one hard drive.
Windows 3.1 through Windows 98 (and bill gates' 1/8 scale clone wini-me) were
based on DOS, they couldn't take advantage of SMP if their life depended on
it. NT through 4.0 had a market share dwarfed by the macintosh.
> 3. Nobody needs them for the usual tasks they are a *waste*
> of resources and economics still applies.
Until moore's law hits atomic resolution, sure. How long that will take is
hotly debated...
> 4. SMP doesn't scale behind 4. Point. (64 hardly makes sense...)
Actually it does, just not with Intel's brain dead memory bus architecture.
EV6 goes to 32-way pretty well.
The question is, at what point is it cheaper to just go to NUMA or clusters.
(And at what point do your trace lengths get long enough that SMP starts
acting like NUMA. And at what point do your cluster interconnects get fast
enough that something like mosix starts acting like numa?)
And the REALLY interesting advance is SMT (hyper-threading), rather than SMP.
How do you go beyond the athlon's three execution cores without running out
of parallel instructions to feed them? Simple, teach the chip about
processes, so it can advance multiple points of execution to keep the cores
fed. This lets you throw a higher transistor budget at the L1 and L2 caches
without encountering diminishing returns as well. It's pretty
straightforward, and at the very least allows dispatching interrupts in
parallel and lets your GUI overlap drawing on the screen with the processing
to figure out what goes on the screen. Between the two of them, even X11
might finally give me smooth mouse scrolling, one of these days... :)
SMP on a chip really is overkill. Why give the multiple processors their own
cache and memory bus interface? Waste of transistors, power, heat, etc...
SMT is minimalist SMP on a chip...
> 5. It will never become a commodity to run highly transactional
> workloads where integrated bunches of 4 make sense. Neiter will
> it be common to solve partial differential equations for aeroplane
> dynamics or to calculate the behaviour of an hydrogen bomb.
No, but it will be common to display bidirectional MP4 compressed video
through an encrypted link, with sound, quite possibly in a window while you
do other stuff with the machine. And some day voice recognition may actually
replace "the clapper" to turn your light off when you get into bed at night...
> One exception could be dedicated rendering CPUs - which is the
> direction where graphics cards are apparently heading - but they
"heading"? Headed. (What did you think your 3D accelerator card was?)
> PS. I'm sick of seeing bunches of PC's which are accidentally in
> the same room nowadays in the list of the 500 fastest computers
> on the world. It makes this list useless...
It shows who has money to throw at the problem, and approximately how much,
which is all it ever really showed...
> If one want's to have a grasp on how the next generation of
> really fast computers will look alike. Well: they will be based
> on Johnson-junctions. TRW will build them (same company
> as Voyager sonde). Look there they don't plan for thousands of CPUs
> they plan for few CPUs in liquid helium:
>
> http://www.trw.com/extlink/1,,,00.html?ExternalTRW=/images/imaps_2000_paper
>.pdf&DIR=2
And cray bathed their circuitry in flourinert decades ago. Liquid Helium
ain't winding up on my desktop any time soon, and my laptop outperforms a
cray-1, and I use it for a dozen variations of text editing (coding,
email...) Not interesting.
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/