Date: Mon, 03 Mar 2008 04:28:13 -0500 From: "Aryeh M. Friedman" <aryeh.friedman@gmail.com> To: Robert Watson <rwatson@FreeBSD.org> Cc: Maxim Sobolev <sobomax@FreeBSD.org>, Jeff Roberson <jeff@FreeBSD.org>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, cvs-src@FreeBSD.org Subject: Re: 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 ... Message-ID: <47CBC4AD.8090100@gmail.com> In-Reply-To: <20080303092335.E66705@fledge.watson.org> References: <200803020758.m227wgH9040483@repoman.freebsd.org> <47CBC127.8010403@FreeBSD.org> <20080303092335.E66705@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47CBC4AD.8090100>