mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
	Baokun Li <libaokun@linux.alibaba.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] block: try slab allocation in bio_alloc_bioset() before mempool
Date: Thu, 16 Jul 2026 07:46:03 +0800	[thread overview]
Message-ID: <da6a57b6-8bbc-4ee6-b3ec-37bcc4db0e44@linux.alibaba.com> (raw)
In-Reply-To: <20260709020145.4011533-1-joseph.qi@linux.alibaba.com>

Gentle ping...

On 7/9/26 10:01 AM, Joseph Qi wrote:
> When the per-CPU bio cache is enabled but empty, bio_alloc_percpu_cache()
> returns NULL and bio_alloc_bioset() falls straight through to the mempool
> fallback:
> 
>     if (unlikely(!bio)) {
>         if (!(saved_gfp & __GFP_DIRECT_RECLAIM))
>             return NULL;
>         ...
>     }
> 
> For non-sleeping allocations (no __GFP_DIRECT_RECLAIM) this returns NULL
> without ever attempting a slab allocation, even when there is plenty of
> free memory.
> 
> Commit b520c4eef83d ("block: split bio_alloc_bioset more clearly into a
> fast and slowpath") introduced this. Before it, a percpu cache miss fell
> through to mempool_alloc(), which attempted the underlying slab allocation
> first and only failed when that slab allocation failed. The restructuring
> dropped the slab attempt that non-sleeping callers of a cache-enabled
> bioset (such as the default fs_bio_set used by bio_alloc()) relied on.
> 
> Try a slab allocation with optimistic GFP_ flags before falling back to
> the mempool whenever the bio is still NULL, so both the cache-empty and
> non-cache paths share the same slab attempt. This restores the previous
> behavior for non-sleeping allocations.
> 
> Fixes: b520c4eef83d ("block: split bio_alloc_bioset more clearly into a fast and slowpath")
> Suggested-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Joseph Qi <joseph.qi@linux.alibaba.com>
> ---
>  block/bio.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/block/bio.c b/block/bio.c
> index f2a5f4d0a9672..982f2e47a4218 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -555,6 +555,14 @@ struct bio *bio_alloc_bioset(struct block_device *bdev, unsigned short nr_vecs,
>  		bio = bio_alloc_percpu_cache(bs);
>  	} else {
>  		opf &= ~REQ_ALLOC_CACHE;
> +	}
> +
> +	/*
> +	 * For a bioset without a percpu cache, or when the percpu cache was
> +	 * empty, try a slab allocation with optimistic GFP_ flags before
> +	 * falling back to the mempool.
> +	 */
> +	if (!bio) {
>  		p = kmem_cache_alloc(bs->bio_slab, gfp);
>  		if (p)
>  			bio = p + bs->front_pad;


  parent reply	other threads:[~2026-07-15 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  2:01 Joseph Qi
2026-07-09  4:48 ` Christoph Hellwig
2026-07-15 23:46 ` Joseph Qi [this message]
2026-07-16 12:12 ` Jens Axboe

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=da6a57b6-8bbc-4ee6-b3ec-37bcc4db0e44@linux.alibaba.com \
    --to=joseph.qi@linux.alibaba.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=libaokun@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@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

Powered by JetHome