From: Zhang Peng <zhangpengpeng0808@gmail.com>
To: jack@suse.cz
Cc: akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, willy@infradead.org, vernhao@tencent.com,
zigiwang@tencent.com, bruzzhang@tencent.com
Subject: Re: [PATCH 0/10] mm: Fix various readahead quirks
Date: Thu, 27 Jun 2024 11:04:56 +0800 [thread overview]
Message-ID: <513c13ea-3568-441c-972c-c5427d076cb9@gmail.com> (raw)
In-Reply-To: <20240625100859.15507-1-jack@suse.cz>
I test this batch of patch with fio, it indeed has a huge sppedup
in sequential read when block size is 4KiB. The result as follow,
for async read, iodepth is set to 128, and other settings
are self-evident.
casename upstream withFix speedup
---------------- -------- -------- -------
randread-4k-sync 48991 47773 -2.4862%
seqread-4k-sync 1162758 1422955 22.3776%
seqread-1024k-sync 1460208 1452522 -0.5264%
randread-4k-libaio 47467 47309 -0.3329%
randread-4k-posixaio 49190 49512 0.6546%
seqread-4k-libaio 1085932 1234635 13.6936%
seqread-1024k-libaio 1423341 1402214 -1.4843%
seqread-4k-posixaio 1165084 1369613 17.5549%
seqread-1024k-posixaio 1435422 1408808 -1.8541%
next prev parent reply other threads:[~2024-06-27 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 10:18 [PATCH 0/10] mm: Fix various readahead quirks Jan Kara
2024-06-25 10:18 ` [PATCH 01/10] readahead: Make sure sync readahead reads needed page Jan Kara
2024-06-25 10:18 ` [PATCH 02/10] filemap: Fix page_cache_next_miss() when no hole found Jan Kara
2024-06-25 10:18 ` [PATCH 03/10] readahead: Properly shorten readahead when falling back to do_page_cache_ra() Jan Kara
2024-06-25 10:18 ` [PATCH 04/10] readahead: Drop pointless index from force_page_cache_ra() Jan Kara
2024-06-25 10:18 ` [PATCH 05/10] readahead: Drop index argument of page_cache_async_readahead() Jan Kara
2024-06-25 10:18 ` [PATCH 06/10] readahead: Drop dead code in page_cache_ra_order() Jan Kara
2024-06-25 10:18 ` [PATCH 07/10] readahead: Drop dead code in ondemand_readahead() Jan Kara
2024-06-25 10:18 ` [PATCH 08/10] readahead: Disentangle async and sync readahead Jan Kara
2024-06-25 10:18 ` [PATCH 09/10] readahead: Fold try_context_readahead() into its single caller Jan Kara
2024-06-25 10:19 ` [PATCH 10/10] readahead: Simplify gotos in page_cache_sync_ra() Jan Kara
2024-06-25 17:12 ` [PATCH 0/10] mm: Fix various readahead quirks Josef Bacik
2024-06-27 3:04 ` Zhang Peng [this message]
2024-06-27 6:10 ` zippermonkey
2024-06-27 21:13 ` Andrew Morton
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=513c13ea-3568-441c-972c-c5427d076cb9@gmail.com \
--to=zhangpengpeng0808@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bruzzhang@tencent.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vernhao@tencent.com \
--cc=willy@infradead.org \
--cc=zigiwang@tencent.com \
/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;
as well as URLs for NNTP newsgroup(s).