From: "Sungjong Seo" <sj1557.seo@samsung.com>
To: "'Anthony Iliopoulos'" <ailiop@suse.com>,
"'Namjae Jeon'" <linkinjeon@kernel.org>,
"'Yuezhang Mo'" <yuezhang.mo@sony.com>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sjdev.seo@gmail.com>, <cpgs@samsung.com>,
<sj1557.seo@samsung.com>
Subject: RE: [PATCH] exfat: enable request merging for dir readahead
Date: Tue, 8 Apr 2025 10:15:35 +0900 [thread overview]
Message-ID: <c2c601dba823$bb2fdf00$318f9d00$@samsung.com> (raw)
In-Reply-To: <20250407102345.50130-1-ailiop@suse.com>
Hi, Anthony
> Directory listings that need to access the inode metadata (e.g. via
> statx to obtain the file types) of large filesystems with lots of
> metadata that aren't yet in dcache, will take a long time due to the
> directory readahead submitting one io request at a time which although
> targeting sequential disk sectors (up to EXFAT_MAX_RA_SIZE) are not
> merged at the block layer.
>
> Add plugging around sb_breadahead so that the requests can be batched
> and submitted jointly to the block layer where they can be merged by the
> io schedulers, instead of having each request individually submitted to
> the hardware queues.
>
> This significantly improves the throughput of directory listings as it
> also minimizes the number of io completions and related handling from
> the device driver side.
Good approach. However, this attempt was in the past Samsung code,
and there was a problem that the latency of directory-related operations
became longer when ra_count is large (maybe, MAX_RA_SIZE).
In the most recent code, blk_flush_plug is being done in units of
pages as follows.
```
blk_start_plug(&plug);
for (i = 0; i < ra_count; i++) {
if (i && !(i & (sects_per_page - 1)))
blk_flush_plug(&plug, false);
sb_breadahead(sb, sec + i);
}
blk_finish_plug(&plug);
```
However, since blk_flush_plug is not exported, it can no longer be used in
module build. It seems that blk_flush_plug needs to be exported or
improved to repeat blk_start_plug and blk_finish_plug in units of pages.
After changing to plug by page unit, could you also compare the throughput?
Thanks
>
> Signed-off-by: Anthony Iliopoulos <ailiop@suse.com>
> ---
> fs/exfat/dir.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/exfat/dir.c b/fs/exfat/dir.c
> index 3103b932b674..a46ab2690b4d 100644
> --- a/fs/exfat/dir.c
> +++ b/fs/exfat/dir.c
> @@ -621,6 +621,7 @@ static int exfat_dir_readahead(struct super_block *sb,
> sector_t sec)
> {
> struct exfat_sb_info *sbi = EXFAT_SB(sb);
> struct buffer_head *bh;
> + struct blk_plug plug;
> unsigned int max_ra_count = EXFAT_MAX_RA_SIZE >> sb-
> >s_blocksize_bits;
> unsigned int page_ra_count = PAGE_SIZE >> sb->s_blocksize_bits;
> unsigned int adj_ra_count = max(sbi->sect_per_clus, page_ra_count);
> @@ -644,8 +645,10 @@ static int exfat_dir_readahead(struct super_block
*sb,
> sector_t sec)
> if (!bh || !buffer_uptodate(bh)) {
> unsigned int i;
>
> + blk_start_plug(&plug);
> for (i = 0; i < ra_count; i++)
> sb_breadahead(sb, (sector_t)(sec + i));
> + blk_finish_plug(&plug);
> }
> brelse(bh);
> return 0;
> --
> 2.49.0
prev parent reply other threads:[~2025-04-08 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250407102359epcas1p1dd23affd903c1ece78ddbfe85d39034e@epcas1p1.samsung.com>
2025-04-07 10:23 ` [PATCH] exfat: enable request merging for dir readahead Anthony Iliopoulos
2025-04-07 13:00 ` Namjae Jeon
2025-04-08 1:15 ` Sungjong Seo [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='c2c601dba823$bb2fdf00$318f9d00$@samsung.com' \
--to=sj1557.seo@samsung.com \
--cc=ailiop@suse.com \
--cc=cpgs@samsung.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sjdev.seo@gmail.com \
--cc=yuezhang.mo@sony.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).