LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22)
@ 2008-01-19 14:05 dAniel hAhler
  2008-01-19 14:52 ` dAniel hAhler
  0 siblings, 1 reply; 6+ messages in thread
From: dAniel hAhler @ 2008-01-19 14:05 UTC (permalink / raw)
  To: LKML

Hello,

I have BOINC running in the background with niceness 19.
With a 2.6.22 kernel, only idle cpu cycles get assigned to this process, as
expected.

But with the 2.6.24 kernel, the BOINC process gets at least about half of
all CPU cycles, even if there's another process (owned by another user)
requesting CPU cycles (e.g. "cat /dev/urandom > /dev/null")

This happens with the Ubuntu kernel (from Hardy) and the daily builds from
http://kernel-archive.buildserver.net/debian-kernel/ (where I've just tested
rc8 now).

It appears that every user (here "boinc" and my user) get the same portion
of the overall CPU cycles, regardless of the process niceness.

Is this expected behaviour?

I'm using an AMD64 3000+ processor. Please ask for additional information, if
you need it (e.g. kernel config).


TESTCASE:
$ cat /dev/urandom > /dev/null &
$ sudo -u another_user nice -n 19 python -c 'i = 0;
while 1:
  i += i
'

EXPECTED RESULT:
The niced process should get nearly no CPU cycles.

ACTUAL RESULT:
The niced process gets about half of the CPU cycles (according to "top").


The bug has been reported for Ubuntu on https://launchpad.net/bugs/177713


-- 
http://daniel.hahler.de/

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2008-01-22  1:59 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-01-19 14:05 Regression with idle cpu cycle handling in 2.6.24 (compared to 2.6.22) dAniel hAhler
2008-01-19 14:52 ` dAniel hAhler
2008-01-20  3:33   ` Dhaval Giani
2008-01-20  4:03     ` Dhaval Giani
2008-01-21 17:18     ` Srivatsa Vaddagiri
2008-01-22  1:59       ` dAniel hAhler

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).