> Sure, it probably is a non issue, but I'm afraid that non issues of today > might become issues of tomorrow. Where does it say that we can never put a > task struct in a movable zone. Task structs are not movable, so they by definition do not belong in movable zones. > memory local to it, and pinned tasks to that CPU in that memory. Then > there can be cases where we remove the CPU and memory together. If you did that you would need to redesign so much of the kernel, changing the mutex code too would be the smallest of your worries. -Andi -- ak@xxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
