linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yu Kuai <yukuai1@huaweicloud.com>
To: Yu Kuai <yukuai1@huaweicloud.com>,
	willy@infradead.org, akpm@linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
	yangerkun@huawei.com, johnny.chenyi@huawei.com,
	"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH RFC] mm/readahead: improve randread performance with readahead disabled
Date: Wed, 23 Jul 2025 17:03:33 +0800	[thread overview]
Message-ID: <416d00a2-1530-3ee7-be31-2a58f5fc70e2@huaweicloud.com> (raw)
In-Reply-To: <19b73b35-1e16-cb7d-d32f-d054d3e66fa0@huaweicloud.com>

Hi,

在 2025/07/14 9:42, Yu Kuai 写道:
> Hi,
> 
> 在 2025/07/01 19:08, Yu Kuai 写道:
>> From: Yu Kuai <yukuai3@huawei.com>
>>
>> We have a workload of random 4k-128k read on a HDD, from iostat we 
>> observed
>> that average request size is 256k+ and bandwidth is 100MB+, this is 
>> because
>> readahead waste lots of disk bandwidth. Hence we disable readahead and
>> performance from user side is indeed much better(2x+), however, from
>> iostat we observed request size is just 4k and bandwidth is just around
>> 40MB.
>>
>> Then we do a simple dd test and found out if readahead is disabled,
>> page_cache_sync_ra() will force to read one page at a time, and this
>> really doesn't make sense because we can just issue user requested size
>> request to disk.
>>
>> Fix this problem by removing the limit to read one page at a time from
>> page_cache_sync_ra(), this way the random read workload can get better
>> performance with readahead disabled.
>>
>> PS: I'm not sure if I miss anything, so this version is RFC
>> Signed-off-by: Yu Kuai <yukuai3@huawei.com>
>> ---
>>   mm/readahead.c | 12 ++++++++++--
>>   1 file changed, 10 insertions(+), 2 deletions(-)
>>
> 
> Friendly ping ...
> 

Friendly ping again ...

>> diff --git a/mm/readahead.c b/mm/readahead.c
>> index 20d36d6b055e..1df85ccba575 100644
>> --- a/mm/readahead.c
>> +++ b/mm/readahead.c
>> @@ -561,13 +561,21 @@ void page_cache_sync_ra(struct readahead_control 
>> *ractl,
>>        * Even if readahead is disabled, issue this request as readahead
>>        * as we'll need it to satisfy the requested range. The forced
>>        * readahead will do the right thing and limit the read to just the
>> -     * requested range, which we'll set to 1 page for this case.
>> +     * requested range.
>>        */
>> -    if (!ra->ra_pages || blk_cgroup_congested()) {
>> +    if (blk_cgroup_congested()) {
>>           if (!ractl->file)
>>               return;
>> +        /*
>> +         * If the cgroup is congested, ensure to do at least 1 page of
>> +         * readahead to make progress on the read.
>> +         */
>>           req_count = 1;
>>           do_forced_ra = true;
>> +    } else if (!ra->ra_pages) {
>> +        if (!ractl->file)
>> +            return;
>> +        do_forced_ra = true;
>>       }
>>       /* be dumb */
>>
> 
> .
> 


      reply	other threads:[~2025-07-23  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01 11:08 [PATCH RFC] mm/readahead: improve randread performance with readahead disabled Yu Kuai
2025-07-14  1:42 ` Yu Kuai
2025-07-23  9:03   ` Yu Kuai [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=416d00a2-1530-3ee7-be31-2a58f5fc70e2@huaweicloud.com \
    --to=yukuai1@huaweicloud.com \
    --cc=akpm@linux-foundation.org \
    --cc=johnny.chenyi@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai3@huawei.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).