From: Christian Brauner <brauner@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>,
"Paul E. McKenney" <paulmck@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Jann Horn <jannh@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] fs,mm: add kmem_cache_create_rcu()
Date: Wed, 28 Aug 2024 14:18:01 +0200 [thread overview]
Message-ID: <20240828-basen-verteidigen-327c7a299ee2@brauner> (raw)
In-Reply-To: <96dd4a75-e83f-4807-b43e-bd5552f6aa6d@suse.cz>
> > @Vlastimil, @Jens, @Linus what do you think?
>
> In the other thread you said it's best to leave such refactoring to
> maintainers and I agree and don't ask you to do the cleanup in order to get
> what you need (and we don't need to rush it either).
I mainly didn't want to wait for that huge refactor to be done before we
get a workable solution for v6.12 since the patch isn't all that huge.
But I'm not shying away from cleanup work I'm the cause of.
So I'm happy to do it for v6.13 as a follow-up but I also don't want to
steal this away from you because it'll probably be a fun task to get to
port everything to struct kmem_cache_args and clean that all up.
next prev parent reply other threads:[~2024-08-28 12:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 15:59 Christian Brauner
2024-08-27 15:59 ` [PATCH v2 1/3] mm: remove unused root_cache argument Christian Brauner
2024-08-27 15:59 ` [PATCH v2 2/3] mm: add kmem_cache_create_rcu() Christian Brauner
2024-08-27 18:33 ` Linus Torvalds
2024-08-27 21:10 ` Vlastimil Babka
2024-08-28 9:47 ` Christian Brauner
2024-08-27 15:59 ` [PATCH v2 3/3] fs: use kmem_cache_create_rcu() Christian Brauner
2024-08-27 16:05 ` [PATCH v2 0/3] fs,mm: add kmem_cache_create_rcu() Christian Brauner
2024-08-27 20:15 ` Vlastimil Babka
2024-08-28 12:18 ` Christian Brauner [this message]
2024-08-28 15:32 ` Vlastimil Babka
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=20240828-basen-verteidigen-327c7a299ee2@brauner \
--to=brauner@kernel.org \
--cc=axboe@kernel.dk \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paulmck@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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