BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Dave Marchevsky <davemarchevsky@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, kernel-team@fb.com, memxor@gmail.com,
	tj@kernel.org
Subject: Re: [PATCH v5 bpf-next 0/9] BPF rbtree next-gen datastructure
Date: Mon, 13 Feb 2023 23:00:16 +0000	[thread overview]
Message-ID: <167632921677.17957.18150265210526463163.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230212092715.1422619-1-davemarchevsky@fb.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Sun, 12 Feb 2023 01:27:06 -0800 you wrote:
> This series adds a rbtree datastructure following the "next-gen
> datastructure" precedent set by recently-added linked-list [0]. This is
> a reimplementation of previous rbtree RFC [1] to use kfunc + kptr
> instead of adding a new map type. This series adds a smaller set of API
> functions than that RFC - just the minimum needed to support current
> cgfifo example scheduler in ongoing sched_ext effort [2], namely:
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next,1/9] bpf: Migrate release_on_unlock logic to non-owning ref semantics
    https://git.kernel.org/bpf/bpf-next/c/6a3cd3318ff6
  - [v5,bpf-next,2/9] bpf: Add basic bpf_rb_{root,node} support
    (no matching commit)
  - [v5,bpf-next,3/9] bpf: Add bpf_rbtree_{add,remove,first} kfuncs
    (no matching commit)
  - [v5,bpf-next,4/9] bpf: Add support for bpf_rb_root and bpf_rb_node in kfunc args
    (no matching commit)
  - [v5,bpf-next,5/9] bpf: Add callback validation to kfunc verifier logic
    (no matching commit)
  - [v5,bpf-next,6/9] bpf: Special verifier handling for bpf_rbtree_{remove, first}
    (no matching commit)
  - [v5,bpf-next,7/9] bpf: Add bpf_rbtree_{add,remove,first} decls to bpf_experimental.h
    (no matching commit)
  - [v5,bpf-next,8/9] selftests/bpf: Add rbtree selftests
    (no matching commit)
  - [v5,bpf-next,9/9] bpf, documentation: Add graph documentation for non-owning refs
    (no matching commit)

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



      parent reply	other threads:[~2023-02-13 23:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-12  9:27 [PATCH v5 bpf-next 0/9] BPF rbtree next-gen datastructure Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 1/9] bpf: Migrate release_on_unlock logic to non-owning ref semantics Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 2/9] bpf: Add basic bpf_rb_{root,node} support Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 3/9] bpf: Add bpf_rbtree_{add,remove,first} kfuncs Dave Marchevsky
2023-02-12 11:21   ` kernel test robot
2023-02-13 20:44     ` Dave Marchevsky
2023-02-13 20:48       ` Nick Desaulniers
2023-02-13 22:17         ` Alexei Starovoitov
2023-02-13 22:33           ` Alexei Starovoitov
2023-02-13 23:31           ` Sami Tolvanen
2023-02-14 11:21             ` Peter Zijlstra
2023-02-14 21:59               ` Sami Tolvanen
2023-02-14 23:59                 ` Alexei Starovoitov
2023-02-15  9:43                   ` Peter Zijlstra
2023-02-15 16:56                     ` Sami Tolvanen
2023-02-12  9:27 ` [PATCH v5 bpf-next 4/9] bpf: Add support for bpf_rb_root and bpf_rb_node in kfunc args Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 5/9] bpf: Add callback validation to kfunc verifier logic Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 6/9] bpf: Special verifier handling for bpf_rbtree_{remove, first} Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 7/9] bpf: Add bpf_rbtree_{add,remove,first} decls to bpf_experimental.h Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 8/9] selftests/bpf: Add rbtree selftests Dave Marchevsky
2023-02-12  9:27 ` [PATCH v5 bpf-next 9/9] bpf, documentation: Add graph documentation for non-owning refs Dave Marchevsky
2023-02-13 23:00 ` patchwork-bot+netdevbpf [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=167632921677.17957.18150265210526463163.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davemarchevsky@fb.com \
    --cc=kernel-team@fb.com \
    --cc=memxor@gmail.com \
    --cc=tj@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