On Sun, 20 May 2007, Duncan wrote:
Date: Sun, 20 May 2007 16:14:45 +0000 (UTC) From: Duncan <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: [gentoo-amd64] Re: Kernel scheduler seems to be making mistakes Peter Humphrey <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sun, 20 May 2007 15:11:52 +0100: So, if you emerge schedutils, one of the binaries you get is called taskset. Once it's emerged, you can read the notes on taskset in /usr/ share/doc/schedutils-*/README.bz2, and/or the taskset manpage. It's pretty simple, to use, however. For example, on a two-core or two-CPU system (CPU0 and CPU1), setting an already running X to run on CPU0 only, on CPU1 only, or on both, is done with the following commands (the number being a CPU bitmask, obviously): taskset -p 1 `pidof X` taskset -p 2 `pidof X` taskset -p 3 `pidof X`
The problem with that is that the boinc client starts a new thread for every work unit.
I've noticed the same problem and I think that it should be up to boinc to set that up properly
-- [EMAIL PROTECTED] mailing list
