From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Andrii Nakryiko <andriin@fb.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@fb.com,
daniel@iogearbox.net, andrii.nakryiko@gmail.com,
kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/6] Implement runqslower BCC tool with BPF CO-RE
Date: Mon, 13 Jan 2020 18:15:00 -0800 [thread overview]
Message-ID: <20200114021459.jjw27v7fdt4f7aza@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200113073143.1779940-1-andriin@fb.com>
On Sun, Jan 12, 2020 at 11:31:37PM -0800, Andrii Nakryiko wrote:
> Based on recent BPF CO-RE, tp_btf, and BPF skeleton changes, re-implement
> BCC-based runqslower tool as a portable pre-compiled BPF CO-RE-based tool.
Looks great. Built it on one kernel and tested on another. CO-RE works :)
Hopefully more tools will be written this way.
Applied. Thanks.
prev parent reply other threads:[~2020-01-14 2:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 7:31 [PATCH v2 bpf-next 0/6] Implement runqslower BCC tool with BPF CO-RE Andrii Nakryiko
2020-01-13 7:31 ` [PATCH v2 bpf-next 1/6] tools: sync uapi/linux/if_link.h Andrii Nakryiko
2020-01-13 7:31 ` [PATCH v2 bpf-next 2/6] libbpf: clean up bpf_helper_defs.h generation output Andrii Nakryiko
2020-01-13 7:31 ` [PATCH v2 bpf-next 3/6] selftests/bpf: conform selftests/bpf Makefile output to libbpf and bpftool Andrii Nakryiko
2020-01-13 7:31 ` [PATCH v2 bpf-next 4/6] bpftool: apply preserve_access_index attribute to all types in BTF dump Andrii Nakryiko
2020-01-13 7:31 ` [PATCH v2 bpf-next 5/6] tools/bpf: add runqslower tool to tools/bpf Andrii Nakryiko
2020-01-14 13:22 ` Jiri Olsa
2020-01-14 17:25 ` Alexei Starovoitov
2020-01-14 18:42 ` Jiri Olsa
2020-01-13 7:31 ` [PATCH v2 bpf-next 6/6] selftests/bpf: build runqslower from selftests Andrii Nakryiko
2020-01-14 2:15 ` 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=20200114021459.jjw27v7fdt4f7aza@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.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).