From: Roman Penyaev <rpenyaev@suse.de>
To: unlisted-recipients:; (no To-header on input)
Cc: Roman Penyaev <rpenyaev@suse.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Davidlohr Bueso <dbueso@suse.de>, Jason Baron <jbaron@akamai.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] perf bench: Add epoll-wait-mp1c benchmark calling epoll_wait(2)
Date: Thu, 3 Jan 2019 16:00:28 +0100 [thread overview]
Message-ID: <20190103150030.17030-1-rpenyaev@suse.de> (raw)
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 <rpenyaev@suse.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Davidlohr Bueso <dbueso@suse.de>
Cc: Jason Baron <jbaron@akamai.com>
Cc: linux-kernel@vger.kernel.org
--
2.19.1
next reply other threads:[~2019-01-03 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 15:00 Roman Penyaev [this message]
2019-01-03 15:00 ` [PATCH 1/2] perf bench: rename epoll-wait bench to epoll-wait-1pmc Roman Penyaev
2019-01-03 15:00 ` [PATCH 2/2] perf bench: Add epoll-wait-mp1c benchmark calling epoll_wait(2) Roman Penyaev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190103150030.17030-1-rpenyaev@suse.de \
--to=rpenyaev@suse.de \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dbueso@suse.de \
--cc=jbaron@akamai.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).