netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v3 bpf-next 00/10] bpf_link observability APIs
Date: Tue, 28 Apr 2020 17:33:24 -0700	[thread overview]
Message-ID: <20200429003324.afboiyqnxjxry6pg@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200429001614.1544-1-andriin@fb.com>

On Tue, Apr 28, 2020 at 05:16:04PM -0700, Andrii Nakryiko wrote:
> This patch series adds various observability APIs to bpf_link:
>   - each bpf_link now gets ID, similar to bpf_map and bpf_prog, by which
>     user-space can iterate over all existing bpf_links and create limited FD
>     from ID;
>   - allows to get extra object information with bpf_link general and
>     type-specific information;
>   - implements `bpf link show` command which lists all active bpf_links in the
>     system;
>   - implements `bpf link pin` allowing to pin bpf_link by ID or from other
>     pinned path.
> 
> v2->v3:
>   - improve spin locking around bpf_link ID (Alexei);
>   - simplify bpf_link_info handling and fix compilation error on sh arch;
> v1->v2:
>   - simplified `bpftool link show` implementation (Quentin);
>   - fixed formatting of bpftool-link.rst (Quentin);
>   - fixed attach type printing logic (Quentin);
> rfc->v1:
>   - dropped read-only bpf_links (Alexei);
>   - fixed bug in bpf_link_cleanup() not removing ID;
>   - fixed bpftool link pinning search logic;
>   - added bash-completion and man page.

Applied, Thanks

      parent reply	other threads:[~2020-04-29  0:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29  0:16 [PATCH v3 bpf-next 00/10] bpf_link observability APIs Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 01/10] bpf: refactor bpf_link update handling Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 02/10] bpf: allocate ID for bpf_link Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 03/10] bpf: support GET_FD_BY_ID and GET_NEXT_ID " Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 04/10] bpf: add support for BPF_OBJ_GET_INFO_BY_FD " Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 05/10] libbpf: add low-level APIs for new bpf_link commands Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 06/10] selftests/bpf: test bpf_link's get_next_id, get_fd_by_id, and get_obj_info Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 07/10] bpftool: expose attach_type-to-string array to non-cgroup code Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 08/10] bpftool: add bpf_link show and pin support Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 09/10] bpftool: add bpftool-link manpage Andrii Nakryiko
2020-04-29  0:16 ` [PATCH v3 bpf-next 10/10] bpftool: add link bash completions Andrii Nakryiko
2020-04-29  0:33 ` 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=20200429003324.afboiyqnxjxry6pg@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).