bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+bpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 0/6] Various BPF helper improvements
Date: Wed, 30 Sep 2020 19:10:03 +0000	[thread overview]
Message-ID: <160149300373.16261.5082951869822951600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1601477936.git.daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Wed, 30 Sep 2020 17:18:14 +0200 you wrote:
> This series adds two BPF helpers, that is, one for retrieving the classid
> of an skb and another one to redirect via the neigh subsystem, and improves
> also the cookie helpers by removing the atomic counter. I've also added
> the bpf_tail_call_static() helper to the libbpf API that we've been using
> in Cilium for a while now, and last but not least the series adds a few
> selftests. For details, please check individual patches, thanks!
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/6] bpf: add classid helper only based on skb->sk
    https://git.kernel.org/bpf/bpf-next/c/b426ce83baa7
  - [bpf-next,v4,2/6] bpf, net: rework cookie generator as per-cpu one
    https://git.kernel.org/bpf/bpf-next/c/92acdc58ab11
  - [bpf-next,v4,3/6] bpf: add redirect_neigh helper as redirect drop-in
    https://git.kernel.org/bpf/bpf-next/c/b4ab31414970
  - [bpf-next,v4,4/6] bpf, libbpf: add bpf_tail_call_static helper for bpf programs
    https://git.kernel.org/bpf/bpf-next/c/0e9f6841f664
  - [bpf-next,v4,5/6] bpf, selftests: use bpf_tail_call_static where appropriate
    https://git.kernel.org/bpf/bpf-next/c/faef26fa444d
  - [bpf-next,v4,6/6] bpf, selftests: add redirect_neigh selftest
    https://git.kernel.org/bpf/bpf-next/c/eef4a011f35d

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-09-30 19:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 15:18 [PATCH bpf-next v4 0/6] Various BPF helper improvements Daniel Borkmann
2020-09-30 15:18 ` [PATCH bpf-next v4 1/6] bpf: add classid helper only based on skb->sk Daniel Borkmann
2020-09-30 15:18 ` [PATCH bpf-next v4 2/6] bpf, net: rework cookie generator as per-cpu one Daniel Borkmann
2020-09-30 15:55   ` Eric Dumazet
2020-09-30 15:18 ` [PATCH bpf-next v4 3/6] bpf: add redirect_neigh helper as redirect drop-in Daniel Borkmann
2020-09-30 16:08   ` David Ahern
2020-09-30 20:56     ` Daniel Borkmann
2020-09-30 15:18 ` [PATCH bpf-next v4 4/6] bpf, libbpf: add bpf_tail_call_static helper for bpf programs Daniel Borkmann
2020-09-30 15:18 ` [PATCH bpf-next v4 5/6] bpf, selftests: use bpf_tail_call_static where appropriate Daniel Borkmann
2020-09-30 17:23   ` Martin KaFai Lau
2020-09-30 15:18 ` [PATCH bpf-next v4 6/6] bpf, selftests: add redirect_neigh selftest Daniel Borkmann
2020-09-30 17:31   ` Martin KaFai Lau
2020-09-30 19:20   ` Alexei Starovoitov
2020-09-30 21:01     ` Daniel Borkmann
2020-09-30 21:12       ` Alexei Starovoitov
2020-09-30 19:10 ` patchwork-bot+bpf [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=160149300373.16261.5082951869822951600.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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).