Re: Automatic parallelization - was Re: LISP Object Oriented?
- From: George Neuner <gneuner2/@comcast.net>
- Date: Wed, 31 Jan 2007 14:26:15 -0500
On 30 Jan 2007 01:43:18 -0800, "Tim Bradshaw" <tfb+google@xxxxxxxx>
wrote:
On Jan 30, 8:34 am, George Neuner <gneune...@xxxxxxxxxxx> wrote:
On 29 Jan 2007 09:06:34 -0800, "mark.hoem...@xxxxxxxxx"
We've already got quad-core general purpose CPUs and larger n-ways on
the horizon.
We already have 8-core CPUs in general use, outside of x86, and have
had for around a year.
I would hardly call UltraSparc a "general use" CPU - it has what now?
0.05% of the market. I concede that it is "general purpose".
The vast majority of multicore machines are dual or quad.
I think it's fairly clear that pretty much any vanilla 4-core CPU will
be starving for memory almost all the time (in particular the kinds of
things that intel and AMD will be pushing this year).
I don't think it's clear at all.
Starvation characteristics depend on the cache performance (frequency
of stall) and the CPU pipeline depth (how long to recover) - there is
nothing "vanilla" about it.
Studies done in the early 90's showed that, with appropriate caching,
from 12-16 CPUs could be supported a from shared memory system without
starvation.
In the late 90's CPUs had made such a huge leap in performance
relative to memory that the number of CPUs that could be served
without starvation dropped to under 4. But this is no longer the
case.
Memory has made a huge comeback in the past few years while core
speeds have remained stable. A modern 2GHz core running over PC-6400
actually has more memory bandwith available than did a 500Mhz R3000
over FPM in 1990.
The impact of a stall is greater on the modern core, but multiple
issue mitigates this somewhat because only the dependent pipeline(s)
need be stalled - unrelated processing can continue.
I am not aware of any recent academic studies on starvation in close
couple shared memory systems - nearly everyone lost interest after the
"Memory Wall" paper was published in the mid 90's.
George
--
for email reply remove "/" from address
.
- References:
- Automatic parallelization - was Re: LISP Object Oriented?
- From: George Neuner
- Re: Automatic parallelization - was Re: LISP Object Oriented?
- From: Tim Bradshaw
- Automatic parallelization - was Re: LISP Object Oriented?
- Prev by Date: Re: Lisp or SCheme
- Next by Date: Re: Automatic parallelization - was Re: LISP Object Oriented?
- Previous by thread: Re: Automatic parallelization - was Re: LISP Object Oriented?
- Next by thread: Re: Automatic parallelization - was Re: LISP Object Oriented?
- Index(es):
Relevant Pages
|