bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>
Cc: <kernel-team@fb.com>, <ast@kernel.org>, <daniel@iogearbox.net>,
	<john.fastabend@gmail.com>, <kpsingh@chromium.org>,
	Song Liu <songliubraving@fb.com>
Subject: [PATCH bpf-next 0/2] introduce BPF_F_SHARE_PE
Date: Tue, 29 Sep 2020 01:47:48 -0700	[thread overview]
Message-ID: <20200929084750.419168-1-songliubraving@fb.com> (raw)

This set introduces BPF_F_SHARE_PE to perf event array for better sharing
of perf event. By default, perf event array removes the perf event when the
map fd used to add the event is closed. With BPF_F_SHARE_PE set, however,
the perf event will stay in the array until it is removed, or the map is
closed.

Song Liu (2):
  bpf: introduce BPF_F_SHARE_PE for perf event array
  selftests/bpf: add tests for BPF_F_SHARE_PE

 include/uapi/linux/bpf.h                      |  3 +
 kernel/bpf/arraymap.c                         | 31 ++++++++-
 tools/include/uapi/linux/bpf.h                |  3 +
 .../bpf/prog_tests/perf_event_share.c         | 68 +++++++++++++++++++
 .../bpf/progs/test_perf_event_share.c         | 44 ++++++++++++
 5 files changed, 147 insertions(+), 2 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/prog_tests/perf_event_share.c
 create mode 100644 tools/testing/selftests/bpf/progs/test_perf_event_share.c

--
2.24.1

             reply	other threads:[~2020-09-29  8:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29  8:47 Song Liu [this message]
2020-09-29  8:47 ` [PATCH bpf-next 1/2] bpf: introduce BPF_F_SHARE_PE for perf event array Song Liu
2020-09-29 14:02   ` Daniel Borkmann
2020-09-29 19:00     ` Alexei Starovoitov
2020-09-29 19:18       ` Daniel Borkmann
2020-09-29 19:28         ` Alexei Starovoitov
2020-09-29 21:08           ` Song Liu
2020-09-29  8:47 ` [PATCH bpf-next 2/2] selftests/bpf: add tests for BPF_F_SHARE_PE Song Liu
2020-09-29 14:08   ` Daniel Borkmann

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=20200929084750.419168-1-songliubraving@fb.com \
    --to=songliubraving@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=netdev@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).