From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, peterz@infradead.org,
tgraf@suug.ch, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next v2 0/3] BPF event output helper improvements
Date: Thu, 14 Jul 2016 18:08:02 +0200 [thread overview]
Message-ID: <cover.1468511632.git.daniel@iogearbox.net> (raw)
This set adds improvements to the BPF event output helper to
support non-linear data sampling, here specifically, for skb
context. For details please see individual patches. The set
is based against net-next tree.
v1 -> v2:
- Integrated and adapted Peter's diff into patch 1, updated
the remaining ones accordingly. Thanks Peter!
Thanks a lot!
Daniel Borkmann (3):
perf, events: add non-linear data support for raw records
bpf, perf: split bpf_perf_event_output
bpf: avoid stack copy and use skb ctx for event output
arch/s390/kernel/perf_cpum_sf.c | 9 ++++--
arch/x86/events/amd/ibs.c | 8 +++--
include/linux/bpf.h | 7 ++++-
include/linux/perf_event.h | 20 ++++++++++++-
include/uapi/linux/bpf.h | 2 ++
kernel/bpf/core.c | 6 ++--
kernel/events/core.c | 66 ++++++++++++++++++++++++++++-------------
kernel/events/internal.h | 16 +++++++---
kernel/trace/bpf_trace.c | 66 +++++++++++++++++++++++------------------
net/core/filter.c | 43 ++++++++++++++++++++++++++-
10 files changed, 180 insertions(+), 63 deletions(-)
--
1.9.3
next reply other threads:[~2016-07-14 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 16:08 Daniel Borkmann [this message]
2016-07-14 16:08 ` [PATCH net-next v2 1/3] perf, events: add non-linear data support for raw records Daniel Borkmann
2016-07-14 16:08 ` [PATCH net-next v2 2/3] bpf, perf: split bpf_perf_event_output Daniel Borkmann
2016-07-14 16:08 ` [PATCH net-next v2 3/3] bpf: avoid stack copy and use skb ctx for event output Daniel Borkmann
2016-07-15 21:24 ` [PATCH net-next v2 0/3] BPF event output helper improvements David Miller
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=cover.1468511632.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tgraf@suug.ch \
/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).