From owner-cvs-all@FreeBSD.ORG Mon Mar 3 09:28:20 2008 Return-Path: Delivered-To: cvs-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A98BE1065672; Mon, 3 Mar 2008 09:28:20 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mta1.srv.hcvlny.cv.net (mta1.srv.hcvlny.cv.net [167.206.4.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7E4708FC1B; Mon, 3 Mar 2008 09:28:20 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from flosoft.no-ip.biz (ool-435559b8.dyn.optonline.net [67.85.89.184]) by mta1.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JX5008KGEB621O0@mta1.srv.hcvlny.cv.net>; Mon, 03 Mar 2008 04:28:19 -0500 (EST) Received: from flosoft.no-ip.biz (localhost [IPv6:::1]) by flosoft.no-ip.biz (8.14.2/8.14.2) with ESMTP id m239SI6s072567; Mon, 03 Mar 2008 04:28:18 -0500 Date: Mon, 03 Mar 2008 04:28:13 -0500 From: "Aryeh M. Friedman" In-reply-to: <20080303092335.E66705@fledge.watson.org> To: Robert Watson Message-id: <47CBC4AD.8090100@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Enigmail-Version: 0.95.6 References: <200803020758.m227wgH9040483@repoman.freebsd.org> <47CBC127.8010403@FreeBSD.org> <20080303092335.E66705@fledge.watson.org> User-Agent: Thunderbird 2.0.0.12 (X11/20080303) Cc: Maxim Sobolev , Jeff Roberson , 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 ... X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2008 09:28:20 -0000 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)