Date: Thu, 02 Jun 2005 23:09:51 +0200 From: David Landgren <david@landgren.net> To: Dave Stephens <hsoftdev17@gmail.com> Cc: freebsd-smp@freebsd.org Subject: Re: Assignmet of CPUs Message-ID: <429F759F.1000403@landgren.net> In-Reply-To: <6845d25a0506020616293991e3@mail.gmail.com> References: <429E67CB.6090901@pacific.net.sg> <6845d25a0506020616293991e3@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
Dave Stephens wrote: > The main problem I see with using temperature is that the ability to > detect CPU temp. is a feature limited to "more modern" machines. It > has become very common even in desktops now a days, but it wouldn't be > available in legacy hardware or custom hardware. > > Just a thought. Well, round-robin startup would at least be better than always using one process to start all processes. That would go some of the way towards improving asymmetric heating. (Says me, whose knowledge of kernel scheduling could be written on the face of a chip and still leave room for footnotes...) David > > On 6/1/05, Erich Dollansky <oceanare@pacific.net.sg> wrote: > [...] >>The last, but hardly used parameter, is the CPU temperature. I noticed >>that FreeBSD tends to use always the same CPU to start a task. This >>makes one CPU real hot while the other stays cool. Taking the CPU >>temperature into account for starting at least new threads would also >>have an advantage of systems with an less then ideal cooling system. >> >>Spreading tasks all over the system with the coolest CPU being the one >>to be started next will make systems a bit cooler.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?429F759F.1000403>