The intention of a new benchmark is to measure events delivery
bandwidth: N threads produce events and 1 thread consumes events
calling epoll_wait(2).

Benchmark does measurements for 8, 16, 32, 64 and 128 threads in
a loop.

This one differs from epoll-wait in that it produces events from
many threads and consumes from one, thus mp1c (many producers
1 consumer).

Roman Penyaev (2):
  perf bench: rename epoll-wait bench to epoll-wait-1pmc
  perf bench: Add epoll-wait-mp1c benchmark calling epoll_wait(2)

 tools/perf/bench/Build                        |   3 +-
 tools/perf/bench/bench.h                      |   3 +-
 .../bench/{epoll-wait.c => epoll-wait-1pmc.c} |   6 +-
 tools/perf/bench/epoll-wait-mp1c.c            | 175 ++++++++++++++++++
 tools/perf/builtin-bench.c                    |   3 +-
 5 files changed, 186 insertions(+), 4 deletions(-)
 rename tools/perf/bench/{epoll-wait.c => epoll-wait-1pmc.c} (98%)
 create mode 100644 tools/perf/bench/epoll-wait-mp1c.c

Signed-off-by: Roman Penyaev <[email protected]>
Cc: Arnaldo Carvalho de Melo <[email protected]>
Cc: Andrew Morton <[email protected]>
Cc: Davidlohr Bueso <[email protected]>
Cc: Jason Baron <[email protected]>
Cc: [email protected]
-- 
2.19.1

Reply via email to