* cpu binding bug?
@ 2001-04-08 21:57 Manfred Spraul
0 siblings, 0 replies; only message in thread
From: Manfred Spraul @ 2001-04-08 21:57 UTC (permalink / raw)
To: linux-kernel
Afaics cpu bindings could allow a thread to run with an "unlimited"
timeslice.
cpu0: one thread running with 'nice==19'.
NICE_TO_TICKS==1.
cpu1: lots of other threads with 'nice==0' (NICE_TO_TICKS==6)
cpu0 will enter schedule() every tick.
can_schedule() returns '0' for all threads bound to cpu1, thus
'recalculate' will be called every tick - that's faster than the threads
on cpu1 can use up their slice.
The currently running thread will run forever.
Is that problem fixed in the patches that allow user space to write
cpus_allowed?
--
Manfred
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-04-08 21:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-08 21:57 cpu binding bug? Manfred Spraul
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).