From: "Paul E. McKenney" <paulmck@kernel.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] rcu_pending
Date: Mon, 19 Aug 2024 16:07:16 -0700 [thread overview]
Message-ID: <0e3c70d8-e2ac-4f71-b155-ef64e25fd415@paulmck-laptop> (raw)
In-Reply-To: <20240819165939.745801-1-kent.overstreet@linux.dev>
On Mon, Aug 19, 2024 at 12:59:26PM -0400, Kent Overstreet wrote:
> New data structure for tracking objects waiting on an RCU grace period.
> Supports regular RCU and SRCU, and possibly other RCU flavors in the
> future. Uses radix trees for tracking pending objects, falling back to
> linked lists on allocation failure.
>
> This gets us a more general replacement for SLAB_TYPESAFE_BY_RCU, and a
> cleaner and slightly faster backend for kvfree_call_rcu(), and
> in the future a faster backend for call_rcu() as well.
>
> There's still some small todo items, mentioned in the relevant patches.
>
> Paul - I'm considering putting this into 6.11 for bcachefs (not the
> patch that switches kvfree_rcu, of course), as I need it rather
> pressingly. Thoughts? I can put it in fs/bcachefs/ if you hate it :)
I am having a hard time imagining it being ready for inclusion in
kernel/rcu by the upcoming (v6.12) merge window, so if you need it then,
you will need to pull it into fs/bcachefs.
Don't get me wrong, it has improved since the June version. And we
can always move it later, if/when appropriate.
And yes, the kvfree_rcu() changes would need some serious performance
evaluation by the people who benefitted from the changes that make
kvfree_rcu() what it is today. So let's please defer that one.
Having the equivalent of SLAB_TYPESAFE_BY_SRCU could be attractive,
but I suspect that there are smaller changes that get us that with the
existing slab allocator.
Thanx, Paul
> Kent Overstreet (9):
> lib/generic-radix-tree.c: genradix_ptr_inlined()
> lib/generic-radix-tree.c: add preallocation
> darray: lift from bcachefs
> vmalloc: is_vmalloc_addr_inlined()
> rcu: delete lockdep_assert_irqs_enabled() assert in
> start_poll_synchronize_rcu_common()
> rcu: rcu_pending
> bcachefs: Rip out freelists from btree key cache
> bcachefs: key cache can now allocate from pending
> rcu: Switch kvfree_rcu() to new rcu_pending
>
> MAINTAINERS | 7 +
> fs/bcachefs/Makefile | 1 -
> fs/bcachefs/btree_key_cache.c | 406 +++----------
> fs/bcachefs/btree_key_cache_types.h | 18 +-
> fs/bcachefs/btree_node_scan_types.h | 2 +-
> fs/bcachefs/btree_types.h | 5 +-
> fs/bcachefs/btree_update.c | 2 +
> fs/bcachefs/btree_write_buffer_types.h | 2 +-
> fs/bcachefs/disk_accounting_types.h | 2 +-
> fs/bcachefs/fsck.c | 2 +-
> fs/bcachefs/journal_io.h | 2 +-
> fs/bcachefs/journal_sb.c | 2 +-
> fs/bcachefs/sb-downgrade.c | 3 +-
> fs/bcachefs/sb-errors_types.h | 2 +-
> fs/bcachefs/sb-members.h | 2 +-
> fs/bcachefs/subvolume.h | 1 -
> fs/bcachefs/subvolume_types.h | 2 +-
> fs/bcachefs/thread_with_file_types.h | 2 +-
> fs/bcachefs/util.h | 29 +-
> {fs/bcachefs => include/linux}/darray.h | 59 +-
> include/linux/darray_types.h | 22 +
> include/linux/generic-radix-tree.h | 106 +++-
> include/linux/mm.h | 7 +
> include/linux/rcu_pending.h | 27 +
> init/main.c | 2 +
> kernel/rcu/Makefile | 2 +-
> kernel/rcu/pending.c | 623 ++++++++++++++++++++
> kernel/rcu/tree.c | 747 ------------------------
> kernel/rcu/update.c | 1 -
> lib/Makefile | 2 +-
> {fs/bcachefs => lib}/darray.c | 12 +-
> lib/generic-radix-tree.c | 80 +--
> mm/vmalloc.c | 4 +-
> 33 files changed, 962 insertions(+), 1224 deletions(-)
> rename {fs/bcachefs => include/linux}/darray.h (66%)
> create mode 100644 include/linux/darray_types.h
> create mode 100644 include/linux/rcu_pending.h
> create mode 100644 kernel/rcu/pending.c
> rename {fs/bcachefs => lib}/darray.c (57%)
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-08-19 23:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 16:59 Kent Overstreet
2024-08-19 16:59 ` [PATCH 1/9] lib/generic-radix-tree.c: genradix_ptr_inlined() Kent Overstreet
2024-08-19 16:59 ` [PATCH 2/9] lib/generic-radix-tree.c: add preallocation Kent Overstreet
2024-08-19 16:59 ` [PATCH 3/9] darray: lift from bcachefs Kent Overstreet
2024-08-21 1:00 ` Jeff Johnson
2024-08-19 16:59 ` [PATCH 4/9] vmalloc: is_vmalloc_addr_inlined() Kent Overstreet
2024-08-19 16:59 ` [PATCH 5/9] rcu: delete lockdep_assert_irqs_enabled() assert in start_poll_synchronize_rcu_common() Kent Overstreet
2024-08-19 21:11 ` Paul E. McKenney
2024-08-19 16:59 ` [PATCH 6/9] rcu: rcu_pending Kent Overstreet
2024-08-19 22:58 ` Paul E. McKenney
2024-08-19 23:59 ` Kent Overstreet
2024-08-26 14:44 ` Paul E. McKenney
2024-08-26 15:17 ` Kent Overstreet
2024-08-26 16:01 ` Paul E. McKenney
2024-08-26 17:09 ` Kent Overstreet
2024-08-30 19:01 ` Paul E. McKenney
2024-09-01 0:03 ` Kent Overstreet
2024-08-19 16:59 ` [PATCH 7/9] bcachefs: Rip out freelists from btree key cache Kent Overstreet
2024-08-19 16:59 ` [PATCH 8/9] bcachefs: key cache can now allocate from pending Kent Overstreet
2024-08-19 16:59 ` [PATCH 9/9] rcu: Switch kvfree_rcu() to new rcu_pending Kent Overstreet
2024-08-19 22:18 ` Paul E. McKenney
2024-08-19 23:05 ` Kent Overstreet
2024-08-19 23:07 ` Paul E. McKenney [this message]
2024-08-19 23:29 ` [PATCH 0/9] rcu_pending Kent Overstreet
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=0e3c70d8-e2ac-4f71-b155-ef64e25fd415@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@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
all inboxes | Powered by JetHome®