Based of my measurement on i386 smp configuration,
If a system has plenty of runnable tasks, schedule() produces
noticable amount of cache misses at runqueue-head traversing and the
goodness calculations.
David S. Miller writes:
> Some of us actually have instrumented it :-) I added a coloring
> mechanism to the task/kstack allocator on sparc64. It made no
> noticable difference whatsoever to any real life measurement I
> attempted.
Did you slide task-struct itself?
--
Computer Systems Laboratory, Fujitsu Labs.
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Alan Cox
- Re: Calling current() from interrupt... Kenn Humborg
- Re: Calling current() from inter... Andi Kleen
- Re: Calling current() from inter... Kenn Humborg
- Re: Calling current() from interrupt cont... Linus Torvalds
- Re: Calling current() from interrupt... Jamie Lokier
- Re: Calling current() from inter... Alan Cox
- Re: Calling current() from inter... David S. Miller
- Re: Calling current() from inter... kumon
- Re: Calling current() from inter... Linus Torvalds
- Re: Calling current() from interrupt cont... yodaiken
- Re: Calling current() from interrupt context Ralf Baechle