Messages in this thread | | | Subject | Re: [Lse-tech] [patch] sched-domain cleanups, sched-2.6.5-rc2-mm2-A3 | Date | Thu, 25 Mar 2004 14:26:35 -0800 | From | Rick Lindsley <> |
| |
There's no way the scheduler can figure out the scheduling and memory use patterns of the new tasks in advance.
True. Four threads may want to stay on the same node because they are sharing a lot of data and working on something in parallel, or they may want to go to different nodes because the only thing they have in common is a control structure that directs their (largely independent but highly synchronized) efforts.
A while ago there was some effort at user-level page replication, which meant you took a hit once but after that you'd effectively migrated a page to your local memory. The longer you stayed put, the more local your RSS got. I seem to recall some bugs or caveats, though. Anybody know the state of that? It might take the burden off the scheduler using a crystal ball and putting it on a 20/20-hindsight VM system instead.
Rick - 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/
| |