I still think it's totally the wrong direction to pollute so many fast paths with this obscure debugging check workaround unconditionally.
cond_resched() is in EVERY sleeping lock and in EVERY memory allocation! And these are really critical paths for many workloads. If you really wanted to do this I think you would first need to define a cond_resched_i_am_not_fast() or somesuch. Or put it all behind some debugging ifdef. -Andi -- a...@linux.intel.com -- Speaking for myself only -- 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/
