From: "changfengnan" <changfengnan@bytedance.com>
To: <axboe@kernel.dk>, <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>
Subject: Re: [PATCH v3 0/2] block: enable per-cpu bio cache by default
Date: Wed, 03 Dec 2025 16:31:02 +0800 [thread overview]
Message-ID: <d9210bcdf73fbe1ac8b6ec132865609a3ed68688.198e8c10.5c50.4606.8f05.84122efb6429@bytedance.com> (raw)
In-Reply-To: <20251114092149.40116-1-changfengnan@bytedance.com>
Ping
> From: "Fengnan Chang"<changfengnan@bytedance.com>
> Date: Fri, Nov 14, 2025, 17:22
> Subject: [PATCH v3 0/2] block: enable per-cpu bio cache by default
> To: <axboe@kernel.dk>, <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>
> Cc: "Fengnan Chang"<changfengnan@bytedance.com>
> 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.
>
> v2:
> enable per-cpu bio cache for passthru IO by default.
>
> v1:
> https://lore.kernel.org/linux-fsdevel/CAPFOzZs5mJ9Ts+TYkhioO8aAYfzevcgw7O3hjexFNb_tM+kEZA@mail.gmail.com/
>
> [1] https://lore.kernel.org/linux-fsdevel/c4bc7c33-b1e1-47d1-9d22-b189c86c6c7d@gmail.com/
>
>
> Fengnan Chang (2):
> block: use bio_alloc_bioset for passthru IO by default
> block: enable per-cpu bio cache by default
>
> block/bio.c | 26 ++++++-----
> block/blk-map.c | 90 ++++++++++++++++-----------------------
> block/fops.c | 4 --
> drivers/nvme/host/ioctl.c | 2 +-
> include/linux/fs.h | 3 --
> io_uring/rw.c | 1 -
> 6 files changed, 49 insertions(+), 77 deletions(-)
>
>
> base-commit: 4a0c9b3391999818e2c5b93719699b255be1f682
> --
> 2.39.5 (Apple Git-154)
>
next prev parent reply other threads:[~2025-12-03 8:31 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 ` changfengnan [this message]
2025-12-03 14:53 ` [PATCH v3 0/2] " 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=d9210bcdf73fbe1ac8b6ec132865609a3ed68688.198e8c10.5c50.4606.8f05.84122efb6429@bytedance.com \
--to=changfengnan@bytedance.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--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