public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	 asml.silence@gmail.com, willy@infradead.org, djwong@kernel.org,
	 hch@infradead.org, ritesh.list@gmail.com,
	linux-fsdevel@vger.kernel.org,  io-uring@vger.kernel.org,
	linux-xfs@vger.kernel.org,  linux-ext4@vger.kernel.org,
	linux-block@vger.kernel.org,  ming.lei@redhat.com,
	linux-nvme@lists.infradead.org,
	 Fengnan Chang <changfengnan@bytedance.com>
Subject: Re: [PATCH v3 0/2] block: enable per-cpu bio cache by default
Date: Wed, 03 Dec 2025 07:53:06 -0700	[thread overview]
Message-ID: <176477358617.834078.6230499988908665369.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251114092149.40116-1-changfengnan@bytedance.com>


On Fri, 14 Nov 2025 17:21:47 +0800, Fengnan Chang wrote:
> For now, per-cpu bio cache was only used in the io_uring + raw block
> device, filesystem also can use this to improve performance.
> After discussion in [1], we think it's better to enable per-cpu bio cache
> by default.
> 
> v3:
> fix some build warnings.
> 
> [...]

Applied, thanks!

[1/2] block: use bio_alloc_bioset for passthru IO by default
      commit: a3ed57376382a72838c5a7bb4705bc6c8b8faf21
[2/2] block: enable per-cpu bio cache by default
      commit: de4590e1f1838345dfd5c93eda01bcff8890607f

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2025-12-03 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14  9:21 [PATCH v3 0/2] block: enable per-cpu bio cache by default Fengnan Chang
2025-11-14  9:21 ` [PATCH v3 1/2] block: use bio_alloc_bioset for passthru IO " Fengnan Chang
2025-11-14  9:21 ` [PATCH v3 2/2] block: enable per-cpu bio cache " Fengnan Chang
2025-12-03  8:31 ` [PATCH v3 0/2] " changfengnan
2025-12-03 14:53 ` Jens Axboe [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=176477358617.834078.6230499988908665369.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=brauner@kernel.org \
    --cc=changfengnan@bytedance.com \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=io-uring@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=ritesh.list@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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