Re: mempool_alloc_bulk and various mempool improvements
From: Vlastimil Babka <hidden>
Date: 2025-11-12 15:57:45
Also in:
lkml
On 11/12/25 16:50, Christoph Hellwig wrote:
On Wed, Nov 12, 2025 at 01:22:01PM +0100, Vlastimil Babka wrote:quoted
On 11/11/25 14:52, Christoph Hellwig wrote:quoted
Hi all, this series adds a bulk version of mempool_alloc that makes allocating multiple objects deadlock safe. The initial users is the blk-crypto-fallback code: https://lore.kernel.org/linux-block/20251031093517.1603379-1-hch@lst.de/ (local) with which v1 was posted, but I also have a few other users in mind.How do we handle this then once it's settled?Good question. I think there is enough mm material now for a merge through an mm tree. If we get it sorted out for this merge window just merging it through mm even when there is no user yet would be easiest as
OK should work hopefully...
the blk-crypto work is probably not going to make this merge window with additional review from Eric and I'll most like have another user for the next merge window as well (block bounce buffering for !STABLE_WRITES dio). Otherwise we'll have to operate with shared branches.
... and we can avoid the need for shared branches that way.