forked from Minki/linux
d2f3f5d2e9
Allows a way of measuring low level kernel implementation of FUTEX_LOCK_PI and FUTEX_UNLOCK_PI. The program comes in two flavors: (i) single futex (default), all threads contend on the same uaddr. For the sake of the benchmark, we call into kernel space even when the lock is uncontended. The kernel will set it to TID, any waters that come in and contend for the pi futex will be handled respectively by the kernel. (ii) -M option for multiple futexes, each thread deals with its own futex. This is a trivial scenario and only measures kernel handling of 0->TID transition. Signed-off-by: Davidlohr Bueso <dbueso@suse.de> Cc: Mel Gorman <mgorman@suse.de> Link: http://lkml.kernel.org/r/1436259353.12255.78.camel@stgolabs.net Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
14 lines
334 B
Plaintext
14 lines
334 B
Plaintext
perf-y += sched-messaging.o
|
|
perf-y += sched-pipe.o
|
|
perf-y += mem-memcpy.o
|
|
perf-y += futex-hash.o
|
|
perf-y += futex-wake.o
|
|
perf-y += futex-wake-parallel.o
|
|
perf-y += futex-requeue.o
|
|
perf-y += futex-lock-pi.o
|
|
|
|
perf-$(CONFIG_X86_64) += mem-memcpy-x86-64-asm.o
|
|
perf-$(CONFIG_X86_64) += mem-memset-x86-64-asm.o
|
|
|
|
perf-$(CONFIG_NUMA) += numa.o
|