From: Yang Shi <yang.shi@linux.alibaba.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@surriel.com>,
gavin.dg@linux.alibaba.com, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: filemap: clear idle flag for writes
Date: Wed, 24 Jun 2020 13:24:08 -0700 [thread overview]
Message-ID: <61fdaf3c-261f-9138-4c4e-a0a859094786@linux.alibaba.com> (raw)
In-Reply-To: <CALvZod6BEw-1=XgwN6RDohnEp1uwmDQwPPvgbtC2H4q-X=Nsig@mail.gmail.com>
On 6/24/20 12:50 PM, Shakeel Butt wrote:
> On Wed, Jun 24, 2020 at 12:18 PM Yang Shi <yang.shi@linux.alibaba.com> wrote:
>>
>>
>> On 6/24/20 11:53 AM, Andrew Morton wrote:
>>> On Thu, 25 Jun 2020 01:43:32 +0800 Yang Shi <yang.shi@linux.alibaba.com> wrote:
>>>
>>>> Since commit bbddabe2e436aa7869b3ac5248df5c14ddde0cbf ("mm: filemap:
>>>> only do access activations on reads"), mark_page_accessed() is called
>>>> for reads only. But the idle flag is cleared by mark_page_accessed() so
>>>> the idle flag won't get cleared if the page is write accessed only.
>>>>
>>>> Basically idle page tracking is used to estimate workingset size of
>>>> workload, noticeable size of workingset might be missed if the idle flag
>>>> is not maintained correctly.
>>>>
>>>> It seems good enough to just clear idle flag for write operations.
>>>>
>>>> ...
>>>>
>>>> --- a/mm/filemap.c
>>>> +++ b/mm/filemap.c
>>>> @@ -41,6 +41,7 @@
>>>> #include <linux/delayacct.h>
>>>> #include <linux/psi.h>
>>>> #include <linux/ramfs.h>
>>>> +#include <linux/page_idle.h>
>>>> #include "internal.h"
>>>>
>>>> #define CREATE_TRACE_POINTS
>>>> @@ -1630,6 +1631,11 @@ struct page *pagecache_get_page(struct address_space *mapping, pgoff_t index,
>>>>
>>>> if (fgp_flags & FGP_ACCESSED)
>>>> mark_page_accessed(page);
>>>> + else if (fgp_flags & FGP_WRITE) {
>>>> + /* Clear idle flag for buffer write */
>>>> + if (page_is_idle(page))
>>>> + clear_page_idle(page);
>>>> + }
>>>>
>>>> no_page:
>>>> if (!page && (fgp_flags & FGP_CREAT)) {
>>> The kerneldoc comment for pagecache_get_page() could do with some
>>> updating - it fails to mention FGP_WRITE, FGP_NOFS and FGP_NOWAIT.
>> Yes, will propose a separate patch later on.
>>
>>> This change seems correct but also will have runtime effects. What are
>>> they?
>> Other than a couple of extra cycles when idle page tracking is enabled,
>> I didn't think of other effects. It should be negligible. The idle flag
>> doesn't play a role in page reclaim algorithm, so it won't have impact
>> on that.
>>
>>
> The only user visible impact will be on idle page tracking users. They
> will get more accurate data.
Thanks for elaborating this.
next prev parent reply other threads:[~2020-06-24 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 17:43 Yang Shi
2020-06-24 18:53 ` Andrew Morton
2020-06-24 19:18 ` Yang Shi
2020-06-24 19:50 ` Shakeel Butt
2020-06-24 20:24 ` Yang Shi [this message]
2020-06-24 19:49 ` Shakeel Butt
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=61fdaf3c-261f-9138-4c4e-a0a859094786@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=gavin.dg@linux.alibaba.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=shakeelb@google.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