cvs commit: src/sys/amd64/amd64 identcpu.c mp_machdep.c src/sys/amd64/include smp.h src/sys/i386/i386 identcpu.c mp_machdep.c src/sys/i386/include smp.h src/sys/ia64/ia64 mp_machdep.c src/sys/kern sched_ule.c subr_smp.c ...

[Aryeh M. Friedman]

Robert Watson wrote:
>
> On Mon, 3 Mar 2008, Maxim Sobolev wrote:
>
>> Cool! I am just curious if the new topology code is flexible enough 
>> to support cores that come and go on the fly? This could be useful in 
>> several scenarios, such as for example when running under multi-core 
>> aware hypervisor (e.g. Niagara), in the cases when pro-active power 
>> manager shuts down some cores to conserve power, in server 
>> applications when one of CPUs either has fried or has been unplugged, 
>> etc.
>
> We have quite a bit of kernel code that expects CPUs never come and 
> go; I've been hoping to interest people in having a devsummit session 
> on CPU hotplugging for a couple of years now. :-) 

Grid computing is an other immediate application (depending on how 
tightly coupled the nodes are of course)