From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/4] bpf: per program stats
Date: Fri, 22 Feb 2019 15:36:40 -0800 [thread overview]
Message-ID: <20190222233644.1487087-1-ast@kernel.org> (raw)
Introduce per program stats to monitor the usage BPF
Alexei Starovoitov (4):
bpf: enable program stats
bpf: expose program stats via bpf_prog_info
tools/bpf: sync bpf.h into tools
tools/bpftool: recognize bpf_prog_info runtime and runcnt
include/linux/bpf.h | 7 ++++
include/linux/filter.h | 16 ++++++++-
include/uapi/linux/bpf.h | 2 ++
kernel/bpf/core.c | 13 +++++++
kernel/bpf/syscall.c | 29 ++++++++++++++--
kernel/bpf/verifier.c | 5 +++
kernel/sysctl.c | 34 +++++++++++++++++++
.../bpftool/Documentation/bpftool-prog.rst | 4 ++-
tools/bpf/bpftool/prog.c | 7 ++++
tools/include/uapi/linux/bpf.h | 2 ++
10 files changed, 115 insertions(+), 4 deletions(-)
--
2.20.0
next reply other threads:[~2019-02-22 23:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 23:36 Alexei Starovoitov [this message]
2019-02-22 23:36 ` [PATCH bpf-next 1/4] bpf: enable program stats Alexei Starovoitov
2019-02-23 0:05 ` Eric Dumazet
2019-02-23 2:29 ` Alexei Starovoitov
2019-02-23 0:34 ` Roman Gushchin
2019-02-23 1:06 ` Daniel Borkmann
2019-02-23 2:38 ` Alexei Starovoitov
2019-02-25 10:36 ` Daniel Borkmann
2019-02-26 4:27 ` Alexei Starovoitov
2019-02-26 15:29 ` Daniel Borkmann
2019-02-27 4:05 ` Alexei Starovoitov
2019-02-23 2:31 ` Alexei Starovoitov
2019-02-22 23:36 ` [PATCH bpf-next 2/4] bpf: expose program stats via bpf_prog_info Alexei Starovoitov
2019-02-22 23:36 ` [PATCH bpf-next 3/4] tools/bpf: sync bpf.h into tools Alexei Starovoitov
2019-02-22 23:36 ` [PATCH bpf-next 4/4] tools/bpftool: recognize bpf_prog_info runtime and runcnt Alexei Starovoitov
2019-02-23 4:17 ` Andrii Nakryiko
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=20190222233644.1487087-1-ast@kernel.org \
--to=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--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).