cpu binding bug?

From: Manfred Spraul (manfred@colorfullife.com)
Date: Sun Apr 08 2001 - 16:57:39 EST

Next message: David: "To: davidel@xmailserver.org [Fwd: Returned mail: see transcript for details]"
Previous message: Miquel van Smoorenburg: "Re: build -->/usr/src/linux"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: David: "To: davidel@xmailserver.org [Fwd: Returned mail: see transcript for details]"
Previous message: Miquel van Smoorenburg: "Re: build -->/usr/src/linux"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:10 EST