Hi, On 07 June 2012 3:01:07 Момчил Иванов wrote:
> temperature. It was constantly increasing from about 33 C. I took a > look at top and saw that both processes were wildly jumping accross > the cores, i.e. CPU0 and CPU1. > > So before reading all the papers about the ULE scheduler and the > source code, I would like to as a simple question: is it that stupid? maybe, maybe not. It could be that the difference is minor as the cache for both kernels is in the same chip. > > I mean, there are just 2 processes running (except of top, X and > ... which should be scheduled occasionally) on 2 cores of one physical > processor. Why sould each be scheduled on a different core each time? > > I did cpuset to pin each to a specific core and got to about a > constant temperature of 72 C. I am affraid to "cpuset -l 0,1 -p <...>" > both of them since I might again get at 100 C. This would be the interesting point? Did it happen because of the dirt or because or the scheduler. > > Is there some remedy? I think that the only remedy available is the one you applied. Erich _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"