Ingo wrote:
> The concept is the following: there are new per-CPU
> system threads (so-called migration threads) that handle
> a per-runqueue 'migration queue'.
Thanks, Ingo.
Could you, or some other kind soul who understands this, to
explain why the following alternative for migrating proceses
currently running on some other cpu wouldn't have been better
(simpler and sufficient):
- add another variable to the task_struct, say "eviction_notice"
- when it comes time to tell a process to migrate, set this
eviction_notice (and then continue without waiting)
- rely on code that fires each time slice on the cpu currently
hosting the evicted process to notice the eviction notice and
serve it (migrate the process instead of giving it yet another
slice).
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:36 EST