All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Song Liu <songliubraving@fb.com>
Cc: bpf <bpf@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH v9 bpf-next 0/3] bpf: sharing bpf runtime stats with
Date: Fri, 1 May 2020 10:56:31 -0700	[thread overview]
Message-ID: <CAADnVQJi9jiB9M7D8vbVAY3T+kb1hFgF373PdGQKtLqPs=5p=Q@mail.gmail.com> (raw)
In-Reply-To: <20200430071506.1408910-1-songliubraving@fb.com>

On Thu, Apr 30, 2020 at 12:15 AM Song Liu <songliubraving@fb.com> wrote:
>
> run_time_ns is a useful stats for BPF programs. However, it is gated by
> sysctl kernel.bpf_stats_enabled. When multiple user space tools are
> toggling kernl.bpf_stats_enabled at the same time, they may confuse each
> other.
>
> Solve this problem with a new BPF command BPF_ENABLE_STATS.
>
> Changes v8 => v9:
>   1. Clean up in selftest (Andrii).
>   2. Not using static variable in test program (Andrii).

Applied. Thanks

      parent reply	other threads:[~2020-05-01 17:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  7:15 [PATCH v9 bpf-next 0/3] bpf: sharing bpf runtime stats with Song Liu
2020-04-30  7:15 ` [PATCH v9 bpf-next 1/3] bpf: sharing bpf runtime stats with BPF_ENABLE_STATS Song Liu
2020-04-30  7:15 ` [PATCH v9 bpf-next 2/3] libbpf: add support for command BPF_ENABLE_STATS Song Liu
2020-05-02 20:00   ` Alexei Starovoitov
2020-05-04 17:45     ` Song Liu
2020-05-04 18:32       ` Andrii Nakryiko
2020-05-10  1:03       ` Alexei Starovoitov
2020-06-21  3:07       ` Andrii Nakryiko
2020-04-30  7:15 ` [PATCH v9 bpf-next 3/3] bpf: add selftest for BPF_ENABLE_STATS Song Liu
2020-04-30 18:16   ` Andrii Nakryiko
2020-05-01 17:56 ` Alexei Starovoitov [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='CAADnVQJi9jiB9M7D8vbVAY3T+kb1hFgF373PdGQKtLqPs=5p=Q@mail.gmail.com' \
    --to=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.