Richard Yao <[email protected]> writes: > Performance analysis of software compilation by Gentoo portage on an > Intel E5-2620 with 64GB of RAM revealed that a sizeable amount of time, > anywhere from 5% to 15%, was spent in get_vmalloc_info(), with at least > 40% of that time spent in the _raw_spin_lock() invoked by it.
I don't think that's the right fix. We want to be able to debug kernels without having to recompile them. And switching locking around dynamically like this is very ugly and hard to maintain. Besides are you sure the spin lock is not needed elsewhere? How are writers to the list protected? -Andi -- [email protected] -- Speaking for myself only -- 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/
