From: Song Liu <songliubraving@fb.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"Kernel Team" <Kernel-team@fb.com>
Subject: Re: [PATCH v7 bpf-next 2/3] libbpf: add support for command BPF_ENABLE_STATS
Date: Wed, 29 Apr 2020 05:36:34 +0000 [thread overview]
Message-ID: <CFA6B73B-32FF-4CFF-A953-7CF897A36868@fb.com> (raw)
In-Reply-To: <CAEf4BzZsQxTW_aQp02cj3L3BofpQ3q76VOX_otA5q1v5EF7q6Q@mail.gmail.com>
> On Apr 28, 2020, at 10:32 PM, Andrii Nakryiko <andrii.nakryiko@gmail.com> wrote:
>
> On Tue, Apr 28, 2020 at 8:59 PM Song Liu <songliubraving@fb.com> wrote:
>>
>> bpf_enable_stats() is added to enable given stats.
>>
>> Signed-off-by: Song Liu <songliubraving@fb.com>
>> ---
>> tools/lib/bpf/bpf.c | 10 ++++++++++
>> tools/lib/bpf/bpf.h | 1 +
>> tools/lib/bpf/libbpf.map | 5 +++++
>> 3 files changed, 16 insertions(+)
>>
>> diff --git a/tools/lib/bpf/bpf.c b/tools/lib/bpf/bpf.c
>> index 5cc1b0785d18..17bb4ad06c0e 100644
>> --- a/tools/lib/bpf/bpf.c
>> +++ b/tools/lib/bpf/bpf.c
>> @@ -826,3 +826,13 @@ int bpf_task_fd_query(int pid, int fd, __u32 flags, char *buf, __u32 *buf_len,
>>
>> return err;
>> }
>> +
>> +int bpf_enable_stats(enum bpf_stats_type type)
>> +{
>> + union bpf_attr attr;
>> +
>> + memset(&attr, 0, sizeof(attr));
>> + attr.enable_stats.type = type;
>> +
>> + return sys_bpf(BPF_ENABLE_STATS, &attr, sizeof(attr));
>> +}
>> diff --git a/tools/lib/bpf/bpf.h b/tools/lib/bpf/bpf.h
>> index 46d47afdd887..5996e64d324c 100644
>> --- a/tools/lib/bpf/bpf.h
>> +++ b/tools/lib/bpf/bpf.h
>> @@ -229,6 +229,7 @@ LIBBPF_API int bpf_load_btf(void *btf, __u32 btf_size, char *log_buf,
>> LIBBPF_API int bpf_task_fd_query(int pid, int fd, __u32 flags, char *buf,
>> __u32 *buf_len, __u32 *prog_id, __u32 *fd_type,
>> __u64 *probe_offset, __u64 *probe_addr);
>> +LIBBPF_API int bpf_enable_stats(enum bpf_stats_type type);
>>
>> #ifdef __cplusplus
>> } /* extern "C" */
>> diff --git a/tools/lib/bpf/libbpf.map b/tools/lib/bpf/libbpf.map
>> index bb8831605b25..ebd946faada5 100644
>> --- a/tools/lib/bpf/libbpf.map
>> +++ b/tools/lib/bpf/libbpf.map
>> @@ -254,3 +254,8 @@ LIBBPF_0.0.8 {
>> bpf_program__set_lsm;
>> bpf_set_link_xdp_fd_opts;
>> } LIBBPF_0.0.7;
>> +
>> +LIBBPF_0.0.9 {
>> + global:
>
> You forgot to pull and rebase. LIBBPF_0.0.9 is already in master.
Hmm.. I pulled earlier today. Let me pull again..
Thanks,
Song
next prev parent reply other threads:[~2020-04-29 5:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 3:58 [PATCH v7 bpf-next 0/3] bpf: sharing bpf runtime stats with Song Liu
2020-04-29 3:58 ` [PATCH v7 bpf-next 1/3] bpf: sharing bpf runtime stats with BPF_ENABLE_STATS Song Liu
2020-04-29 4:39 ` Alexei Starovoitov
2020-04-29 3:58 ` [PATCH v7 bpf-next 2/3] libbpf: add support for command BPF_ENABLE_STATS Song Liu
2020-04-29 5:32 ` Andrii Nakryiko
2020-04-29 5:36 ` Song Liu [this message]
2020-04-29 3:58 ` [PATCH v7 bpf-next 3/3] bpf: add selftest for BPF_ENABLE_STATS Song Liu
2020-04-29 4:57 ` Alexei Starovoitov
2020-04-29 5:32 ` Song Liu
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=CFA6B73B-32FF-4CFF-A953-7CF897A36868@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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).