On Thu, 2013-02-21 at 17:08 +0800, Michael Wang wrote: > But is this patch set really cause regression on your Q6600? It may > sacrificed some thing, but I still think it will benefit far more, > especially on huge systems.
We spread on FORK/EXEC, and will no longer will pull communicating tasks back to a shared cache with the new logic preferring to leave wakee remote, so while no, I haven't tested (will try to find round tuit) it seems it _must_ hurt. Dragging data from one llc to the other on Q6600 hurts a LOT. Every time a client and server are cross llc, it's a huge hit. The previous logic pulled communicating tasks together right when it matters the most, intermittent load... or interactive use. -Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
