On Wed, May 25, 2016 at 04:18:03PM +0800, Pan Xinhui wrote: > _____test________________spinlcok______________pv-qspinlcok_____ > |futex hash | 556370 ops | 629634 ops | > |futex lock-pi | 362 ops | 367 ops | > > scheduler test: > Test how many loops of schedule() can finish within 10 seconds on all cpus. > > _____test________________spinlcok______________pv-qspinlcok_____ > |schedule() loops| 322811921 | 311449290 | > > kernel compiling test: > build a linux kernel image to see how long it took > > _____test________________spinlcok______________pv-qspinlcok_____ > | compiling takes| 22m | 22m | s/spinlcok/spinlock/ Is 'spinlcok' the current test-and-set lock? And what about regular qspinlock, in case of !SHARED_PROCESSOR? _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
