From: Liu Shixin <liushixin2@huawei.com>
To: Jan Kara <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] mm/readahead: limit sync readahead while too many active refault
Date: Thu, 1 Feb 2024 18:41:30 +0800 [thread overview]
Message-ID: <c768cab9-4ccb-9618-24a8-b51d3f141340@huawei.com> (raw)
In-Reply-To: <20240201093749.ll7uzgt7ixy7kkhw@quack3>
On 2024/2/1 17:37, Jan Kara wrote:
> On Thu 01-02-24 18:08:35, Liu Shixin wrote:
>> When the pagefault is not for write and the refault distance is close,
>> the page will be activated directly. If there are too many such pages in
>> a file, that means the pages may be reclaimed immediately.
>> In such situation, there is no positive effect to read-ahead since it will
>> only waste IO. So collect the number of such pages and when the number is
>> too large, stop bothering with read-ahead for a while until it decreased
>> automatically.
>>
>> Define 'too large' as 10000 experientially, which can solves the problem
>> and does not affect by the occasional active refault.
>>
>> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
> So I'm not convinced this new logic is needed. We already have
> ra->mmap_miss which gets incremented when a page fault has to read the page
> (and decremented when a page fault found the page already in cache). This
> should already work to detect trashing as well, shouldn't it? If it does
> not, why?
>
> Honza
ra->mmap_miss doesn't help, it increased only one in do_sync_mmap_readahead()
and then decreased one for every page in filemap_map_pages(). So in this scenario,
it can't exceed MMAP_LOTSAMISS.
Thanks,
>
>> ---
>> include/linux/fs.h | 2 ++
>> include/linux/pagemap.h | 1 +
>> mm/filemap.c | 16 ++++++++++++++++
>> mm/readahead.c | 4 ++++
>> 4 files changed, 23 insertions(+)
>>
>> diff --git a/include/linux/fs.h b/include/linux/fs.h
>> index ed5966a704951..f2a1825442f5a 100644
>> --- a/include/linux/fs.h
>> +++ b/include/linux/fs.h
>> @@ -960,6 +960,7 @@ struct fown_struct {
>> * the first of these pages is accessed.
>> * @ra_pages: Maximum size of a readahead request, copied from the bdi.
>> * @mmap_miss: How many mmap accesses missed in the page cache.
>> + * @active_refault: Number of active page refault.
>> * @prev_pos: The last byte in the most recent read request.
>> *
>> * When this structure is passed to ->readahead(), the "most recent"
>> @@ -971,6 +972,7 @@ struct file_ra_state {
>> unsigned int async_size;
>> unsigned int ra_pages;
>> unsigned int mmap_miss;
>> + unsigned int active_refault;
>> loff_t prev_pos;
>> };
>>
>> diff --git a/include/linux/pagemap.h b/include/linux/pagemap.h
>> index 2df35e65557d2..da9eaf985dec4 100644
>> --- a/include/linux/pagemap.h
>> +++ b/include/linux/pagemap.h
>> @@ -1256,6 +1256,7 @@ struct readahead_control {
>> pgoff_t _index;
>> unsigned int _nr_pages;
>> unsigned int _batch_count;
>> + unsigned int _active_refault;
>> bool _workingset;
>> unsigned long _pflags;
>> };
>> diff --git a/mm/filemap.c b/mm/filemap.c
>> index 750e779c23db7..4de80592ab270 100644
>> --- a/mm/filemap.c
>> +++ b/mm/filemap.c
>> @@ -3037,6 +3037,7 @@ loff_t mapping_seek_hole_data(struct address_space *mapping, loff_t start,
>>
>> #ifdef CONFIG_MMU
>> #define MMAP_LOTSAMISS (100)
>> +#define ACTIVE_REFAULT_LIMIT (10000)
>> /*
>> * lock_folio_maybe_drop_mmap - lock the page, possibly dropping the mmap_lock
>> * @vmf - the vm_fault for this fault.
>> @@ -3142,6 +3143,18 @@ static struct file *do_sync_mmap_readahead(struct vm_fault *vmf)
>> if (mmap_miss > MMAP_LOTSAMISS)
>> return fpin;
>>
>> + ractl._active_refault = READ_ONCE(ra->active_refault);
>> + if (ractl._active_refault)
>> + WRITE_ONCE(ra->active_refault, --ractl._active_refault);
>> +
>> + /*
>> + * If there are a lot of refault of active pages in this file,
>> + * that means the memory reclaim is ongoing. Stop bothering with
>> + * read-ahead since it will only waste IO.
>> + */
>> + if (ractl._active_refault >= ACTIVE_REFAULT_LIMIT)
>> + return fpin;
>> +
>> /*
>> * mmap read-around
>> */
>> @@ -3151,6 +3164,9 @@ static struct file *do_sync_mmap_readahead(struct vm_fault *vmf)
>> ra->async_size = ra->ra_pages / 4;
>> ractl._index = ra->start;
>> page_cache_ra_order(&ractl, ra, 0);
>> +
>> + WRITE_ONCE(ra->active_refault, ractl._active_refault);
>> +
>> return fpin;
>> }
>>
>> diff --git a/mm/readahead.c b/mm/readahead.c
>> index cc4abb67eb223..d79bb70a232c4 100644
>> --- a/mm/readahead.c
>> +++ b/mm/readahead.c
>> @@ -263,6 +263,10 @@ void page_cache_ra_unbounded(struct readahead_control *ractl,
>> folio_set_readahead(folio);
>> ractl->_workingset |= folio_test_workingset(folio);
>> ractl->_nr_pages++;
>> + if (unlikely(folio_test_workingset(folio)))
>> + ractl->_active_refault++;
>> + else if (unlikely(ractl->_active_refault))
>> + ractl->_active_refault--;
>> }
>>
>> /*
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2024-02-01 10:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:08 [PATCH 0/2] Fix I/O high when memory almost met memcg limit Liu Shixin
2024-02-01 10:08 ` [PATCH 1/2] mm/readahead: stop readahead loop if memcg charge fails Liu Shixin
2024-02-01 9:28 ` Jan Kara
2024-02-01 13:47 ` Matthew Wilcox
2024-02-01 13:52 ` Jan Kara
2024-02-01 13:53 ` Matthew Wilcox
2024-02-01 10:08 ` [PATCH 2/2] mm/readahead: limit sync readahead while too many active refault Liu Shixin
2024-02-01 9:37 ` Jan Kara
2024-02-01 10:41 ` Liu Shixin [this message]
2024-02-01 17:31 ` Jan Kara
2024-02-02 1:25 ` Liu Shixin
2024-02-02 9:02 ` Liu Shixin
2024-02-29 9:01 ` Liu Shixin
2024-03-05 7:07 ` Liu Shixin
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=c768cab9-4ccb-9618-24a8-b51d3f141340@huawei.com \
--to=liushixin2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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