From: Daniel Borkmann <daniel@iogearbox.net>
To: alexei.starovoitov@gmail.com
Cc: peterz@infradead.org, paulmck@linux.vnet.ibm.com,
will.deacon@arm.com, acme@redhat.com, yhs@fb.com,
john.fastabend@gmail.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH bpf-next v2 0/2] improve and fix barriers for walking perf ring buffer
Date: Fri, 19 Oct 2018 15:51:01 +0200 [thread overview]
Message-ID: <20181019135103.3602-1-daniel@iogearbox.net> (raw)
This set first adds smp_* barrier variants to tools infrastructure
and updates perf and libbpf to make use of them. For details, please
see individual patches, thanks!
Arnaldo, if there are no objections, could this be routed via bpf-next
with Acked-by's due to later dependencies in libbpf? Alternatively,
I could also get the 2nd patch out during merge window, but perhaps
it's okay to do in one go as there shouldn't be much conflict in perf
itself.
Thanks!
v1 -> v2:
- add common helper and switch to acquire/release variants
when possible, thanks Peter!
Daniel Borkmann (2):
tools, perf: add and use optimized ring_buffer_{read_head,write_tail} helpers
bpf, libbpf: use correct barriers in perf ring buffer walk
tools/arch/arm64/include/asm/barrier.h | 70 +++++++++++++++++++++++++++++
tools/arch/ia64/include/asm/barrier.h | 13 ++++++
tools/arch/powerpc/include/asm/barrier.h | 16 +++++++
tools/arch/s390/include/asm/barrier.h | 13 ++++++
tools/arch/sparc/include/asm/barrier_64.h | 13 ++++++
tools/arch/x86/include/asm/barrier.h | 14 ++++++
tools/include/asm/barrier.h | 35 +++++++++++++++
tools/include/linux/ring_buffer.h | 73 +++++++++++++++++++++++++++++++
tools/lib/bpf/libbpf.c | 10 ++---
tools/perf/util/mmap.h | 15 ++-----
10 files changed, 254 insertions(+), 18 deletions(-)
create mode 100644 tools/include/linux/ring_buffer.h
--
2.9.5
next reply other threads:[~2018-10-19 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 13:51 Daniel Borkmann [this message]
2018-10-19 13:51 ` [PATCH bpf-next v2 1/2] tools, perf: add and use optimized ring_buffer_{read_head,write_tail} helpers Daniel Borkmann
2018-10-19 13:51 ` [PATCH bpf-next v2 2/2] bpf, libbpf: use correct barriers in perf ring buffer walk Daniel Borkmann
2018-10-19 20:45 ` [PATCH bpf-next v2 0/2] improve and fix barriers for walking perf ring buffer Alexei Starovoitov
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=20181019135103.3602-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=acme@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
--cc=yhs@fb.com \
/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