From: Song Liu <songliubraving@fb.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Networking <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>,
"ast@kernel.org" <ast@kernel.org>,
"mcgrof@kernel.org" <mcgrof@kernel.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"yzaikin@google.com" <yzaikin@google.com>
Subject: Re: [PATCH v2 bpf-next] bpf: sharing bpf runtime stats with /dev/bpf_stats
Date: Tue, 17 Mar 2020 20:04:45 +0000 [thread overview]
Message-ID: <E936DB84-3CD8-44C7-ACA6-900C220138ED@fb.com> (raw)
In-Reply-To: <920839AF-AC7A-4CD3-975F-111C3C6F75B9@fb.com>
> On Mar 17, 2020, at 12:54 PM, Song Liu <songliubraving@fb.com> wrote:
>
>
>
>> On Mar 17, 2020, at 12:30 PM, Daniel Borkmann <daniel@iogearbox.net> wrote:
>>
>> On 3/16/20 9:33 PM, Song Liu wrote:
>>> Currently, sysctl kernel.bpf_stats_enabled controls BPF runtime stats.
>>> Typical userspace tools use kernel.bpf_stats_enabled as follows:
>>> 1. Enable kernel.bpf_stats_enabled;
>>> 2. Check program run_time_ns;
>>> 3. Sleep for the monitoring period;
>>> 4. Check program run_time_ns again, calculate the difference;
>>> 5. Disable kernel.bpf_stats_enabled.
>>> The problem with this approach is that only one userspace tool can toggle
>>> this sysctl. If multiple tools toggle the sysctl at the same time, the
>>> measurement may be inaccurate.
>>> To fix this problem while keep backward compatibility, introduce a new
>>> bpf command BPF_ENABLE_RUNTIME_STATS. On success, this command enables
>>> run_time_ns stats and returns a valid fd.
>>> With BPF_ENABLE_RUNTIME_STATS, user space tool would have the following
>>> flow:
>>> 1. Get a fd with BPF_ENABLE_RUNTIME_STATS, and make sure it is valid;
>>> 2. Check program run_time_ns;
>>> 3. Sleep for the monitoring period;
>>> 4. Check program run_time_ns again, calculate the difference;
>>> 5. Close the fd.
>>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>
>> Hmm, I see no relation to /dev/bpf_stats anymore, yet the subject still talks
>> about it?
>
> My fault. Will fix..
>
>>
>> Also, should this have bpftool integration now that we have `bpftool prog profile`
>> support? Would be nice to then fetch the related stats via bpf_prog_info, so users
>> can consume this in an easy way.
>
> We can add "run_time_ns" as a metric to "bpftool prog profile". But the
> mechanism is not the same though. Let me think about this.
Btw, I plan to add this in separate set. Please let me know if it
preferable to have them in the same set.
Thanks,
Song
prev parent reply other threads:[~2020-03-17 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 20:33 [PATCH v2 bpf-next] bpf: sharing bpf runtime stats with /dev/bpf_stats Song Liu
2020-03-17 19:30 ` Daniel Borkmann
2020-03-17 19:54 ` Song Liu
2020-03-17 20:03 ` Daniel Borkmann
2020-03-17 20:13 ` Song Liu
2020-03-17 21:47 ` Daniel Borkmann
2020-03-17 23:08 ` Song Liu
2020-03-18 6:33 ` Song Liu
2020-03-18 20:58 ` Daniel Borkmann
2020-03-18 21:20 ` Song Liu
2020-03-18 22:29 ` Stanislav Fomichev
2020-03-18 23:45 ` Song Liu
2020-03-17 20:04 ` Song Liu [this message]
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=E936DB84-3CD8-44C7-ACA6-900C220138ED@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yzaikin@google.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;
as well as URLs for NNTP newsgroup(s).