From: Christoph Hellwig <hch@infradead.org>
To: Fengnan Chang <changfengnan@bytedance.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ritesh Harjani <ritesh.list@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
"Darrick J. Wong" <djwong@kernel.org>,
brauner@kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] iomap: allow iomap using the per-cpu bio cache
Date: Mon, 25 Aug 2025 03:47:57 -0700 [thread overview]
Message-ID: <aKw_XSEEFVG4n79_@infradead.org> (raw)
In-Reply-To: <CAPFOzZvBvHWHUwNLnH+Ss90OMdu91oZsSD0D7_ncjVh0pF29rQ@mail.gmail.com>
On Mon, Aug 25, 2025 at 05:41:57PM +0800, Fengnan Chang wrote:
> I'm test random direct read performance on io_uring+ext4, and try
> compare to io_uring+ raw blkdev, io_uring+ext4 is quite poor, I'm try to
> improve this, I found ext4 is quite different with blkdev when run
> bio_alloc_bioset. It's beacuse blkdev ext4 use percpu bio cache, but ext4
> path not. So I make this modify.
> My test command is:
> /fio/t/io_uring -p0 -d128 -b4096 -s1 -c1 -F1 -B1 -R1 -X1 -n1 -P1 -t0
> /data01/testfile
> Without this patch:
> BW is 1950MB
> with this patch
> BW is 2001MB.
Interesting. This is why the not yet merged ext4 iomap patches I guess?
Do you see similar numbers with XFS?
>
next prev parent reply other threads:[~2025-08-25 10:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 8:26 [PATCH] iomap: allow iomap using the per-cpu bio cache Fengnan Chang
2025-08-22 15:05 ` Darrick J. Wong
2025-08-22 15:42 ` Matthew Wilcox
2025-08-22 16:07 ` Ritesh Harjani
2025-08-22 16:51 ` Matthew Wilcox
2025-08-23 4:15 ` Ritesh Harjani
2025-08-25 8:51 ` Fengnan Chang
2025-08-25 9:21 ` Christoph Hellwig
2025-08-25 9:41 ` Fengnan Chang
2025-08-25 10:47 ` Christoph Hellwig [this message]
2025-08-26 9:46 ` Fengnan Chang
2025-08-26 13:15 ` Christoph Hellwig
2025-08-26 16:53 ` Ritesh Harjani
2025-08-29 4:26 ` [External] " Fengnan Chang
2025-09-03 8:28 ` Fengnan Chang
2025-09-06 4:25 ` Ritesh Harjani
2025-09-03 9:53 ` Pavel Begunkov
[not found] ` <CAPFOzZtaKcaSsvUfjiJL2TOwMy-jUkMdboEmp++-USvoUoqjYA@mail.gmail.com>
[not found] ` <879fb17c-e6d6-4b1b-bee5-9087ba24a4f2@gmail.com>
2025-09-10 10:52 ` [External] " Fengnan Chang
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=aKw_XSEEFVG4n79_@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=changfengnan@bytedance.com \
--cc=djwong@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.