Re: difference between this and that
- From: Peter Jeremy <peterjeremy@xxxxxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 19:45:53 +1100
On Mon, Mar 17, 2008 at 08:52:39PM -0400, Chuck Robey wrote:
I was giving some thought recently, to the trend towards adding more and
more cores to a single chip, and wondering if maybe, in the next years
ahead, if we wouldn't be seeing things that sound loony today, like a 4096
core motherboard.
Actually, there was a bit of a side-thread about this sort of thing on
the CVS mailing lists a couple of weeks ago. Definitely lots of cores
per system are on the way. You can buy a system with 64 hardware
threads from Sun today. A 128-thread system (dual T-2) will arrive
RSN and Sun have said they intend to double the threads-per-chip every
year. 4096 cores is still a way off and it's not currently clear what
will drive these sort of systems into the mainstream.
One problem is that FreeBSD currently assumes that a CPU mask will fit
into a long - this limits FreeBSD to 32 cores on arm/i386/ppc and 64
cores elsewhere. Getting rid of this limit is going to take some work.
With this in mind, could I ask for a little bit of discussion on the
differences between the SMP management that FreeBAD, and several other OSes
perform, and the things that stuff like Ganglia
As a simplification and if you consider that SMP systems are moving to
NUMA, the difference is mainly a matter of scale: There is an
additional knee in the cost of process migration and RAM access
between different CPU cores depending on whether they are on the same
chip, different chips within the same host or different hosts.
--
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
Attachment:
pgp1OVKpYAFDP.pgp
Description: PGP signature
- References:
- difference between this and that
- From: Chuck Robey
- difference between this and that
- Prev by Date: Re: Power-Mgt (Was: Re: cvs commit: src/sys/i386/cpufreq est.c )
- Next by Date: Re: Power-Mgt (Was: Re: cvs commit: src/sys/i386/cpufreq est.c )
- Previous by thread: difference between this and that
- Index(es):
Relevant Pages
- Re: processors of the future: super-computer-on-a-chip?
... " How many cores do you think a chip could have, lets say 10 or 20+ years from now?
... relegating single-threaded performance to the back seat of its POWER architecture:
instead, after pioneering dual-core products 5 years ago it has been steadily improving their single-threaded
performance. ... Sure, there will be a few applications that could make really good use of huge
numbers of slower cores, but will they fund the associated development sufficiently to overcome
the resources available to develop commodity products? ... [end quote] ... (comp.arch) - Re: How to develop a random number generation device
... chip, and something new will be required to manage them. ... I think that the
number of virtual cores will grow faster than the ... One CPU would be the manager,
... I'm happy to accept that doing things in hardware is often more reliable than doing things
in software (I work with small embedded systems - I know when reliability is important, and I
know about achieving it in practical systems). ... (sci.electronics.design) - Re: How to develop a random number generation device
... chip, and something new will be required to manage them. ... I think that the
number of virtual cores will grow faster than the ... One CPU would be the manager,
... embedded systems - I know when reliability is important, ... (sci.electronics.design) - Re: processors of the future: super-computer-on-a-chip?
... " How many cores do you think a chip could have, lets say 10 or 20+ years from now?
... Just because it's become harder to improve single-thread performance doesn't mean that
it's no longer useful to and that taking the path of least hardware resistance is The Right Thing
To Do. ... In fact, one could argue that because single-threaded operation characterizes such
a large percentage of today's applications, and because software has historically changed so slowly compared
with hardware, then there's relatively little reason to push multiple cores per chip beyond *at
most* a few dozen for the immediate future while continuing to devote significant concentration to improving
single-thread performance too. ... (comp.arch) - Re: PA-Semi
... >that the Inquirer claims for the PA Semi chip? ... the company did not say
what manufacturing process technology the ... >improvement over the current high-end
cores as far as FLOPS/Watts ... (comp.arch)