Longman Thanks for your suggestion. We will look for real scenario to test, and could you please introduce some benchmarks on spinlock ?
Regards Ling > > Your new spinlock code completely change the API and the semantics of the > existing spinlock calls. That requires changes to thousands of places > throughout the whole kernel. It also increases the size of the spinlock from > 4 bytes to 32 bytes. It is basically a no-go. > > However, if you can improve the performance within the existing API and > locking semantics, it will be much more acceptable. > > Cheers, > Longman -- 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/
