On Sat, Jun 09, 2007 at 09:10:51PM -0700, dean gaudet wrote: > ok i've narrowed it some... maybe. > in commit 8ef8286689c6b5bc76212437b85bdd2ba749ee44 things work fine, numa > policy is respected... > the very next commit bc56bba8f31bd99f350a5ebfd43d50f411b620c7 breaks shm > badly causing the test program to oops the kernel. > commit 516dffdcd8827a40532798602830dfcfc672294c fixes that breakage but > numa policy is no longer respected. > i've added the authors of those two commits to the recipient list and > reattached the test program. hopefully someone can shed light on the > problem.
Thanks, this helps a lot. -- wli - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
