Re: Calling current() from interrupt context

From: kumon@flab.fujitsu.co.jp
Date: Tue Oct 10 2000 - 07:25:31 EST

Next message: Jeff Garzik: "Re: getting "struct pci_dev" from "struct netdevice""
Previous message: Phillips, Mike: "RE: getting "struct pci_dev" from "struct netdevice""
In reply to: David S. Miller: "Re: Calling current() from interrupt context"
Next in thread: Linus Torvalds: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

Next message: Jeff Garzik: "Re: getting "struct pci_dev" from "struct netdevice""
Previous message: Phillips, Mike: "RE: getting "struct pci_dev" from "struct netdevice""
In reply to: David S. Miller: "Re: Calling current() from interrupt context"
Next in thread: Linus Torvalds: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:15 EST