From: Ying Han <yinghan@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rik van Riel <riel@redhat.com>, Hillf Danton <dhillf@gmail.com>,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] Revert "mm: vmscan: fix misused nr_reclaimed in shrink_mem_cgroup_zone()"
Date: Mon, 9 Apr 2012 14:23:11 -0700 [thread overview]
Message-ID: <CALWz4ixm+s8tS6cHcpac4MNshB9GiZrpuQO+hjY1rOqEA=o-_w@mail.gmail.com> (raw)
In-Reply-To: <20120409125055.c6f6fdf0.akpm@linux-foundation.org>
On Mon, Apr 9, 2012 at 12:50 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Mon, 9 Apr 2012 12:42:04 -0700
> Ying Han <yinghan@google.com> wrote:
>
>> This reverts commit c38446cc65e1f2b3eb8630c53943b94c4f65f670.
>>
>> Before the commit, the code makes senses to me but not after the commit. The
>> "nr_reclaimed" is the number of pages reclaimed by scanning through the memcg's
>> lru lists. The "nr_to_reclaim" is the target value for the whole function. For
>> example, we like to early break the reclaim if reclaimed 32 pages under direct
>> reclaim (not DEF_PRIORITY).
>>
>> After the reverted commit, the target "nr_to_reclaim" is decremented each time
>> by "nr_reclaimed" but we still use it to compare the "nr_reclaimed". It just
>> doesn't make sense to me...
>>
>> Signed-off-by: Ying Han <yinghan@google.com>
>> ---
>> mm/vmscan.c | 7 +------
>> 1 files changed, 1 insertions(+), 6 deletions(-)
>>
>> diff --git a/mm/vmscan.c b/mm/vmscan.c
>> index 33c332b..1a51868 100644
>> --- a/mm/vmscan.c
>> +++ b/mm/vmscan.c
>> @@ -2107,12 +2107,7 @@ restart:
>> * with multiple processes reclaiming pages, the total
>> * freeing target can get unreasonably large.
>> */
>> - if (nr_reclaimed >= nr_to_reclaim)
>> - nr_to_reclaim = 0;
>> - else
>> - nr_to_reclaim -= nr_reclaimed;
>> -
>> - if (!nr_to_reclaim && priority < DEF_PRIORITY)
>> + if (nr_reclaimed >= nr_to_reclaim && priority < DEF_PRIORITY)
>> break;
>> }
>> blk_finish_plug(&plug);
>
> This code is all within a loop: the "goto restart" thing. We reset
> nr_reclaimed to zero each time around that loop. nr_to_reclaim is (or
> rather, was) constant throughout the entire function.
>
> Comparing nr_reclaimed (whcih is reset each time around the loop) to
> nr_to_reclaim made no sense.
>
> I think the code as it stands is ugly. It would be better to make
> nr_to_reclaim a const and to add another local total_reclaimed, and
> compare that with nr_to_reclaim.
Ok, I will resend the patch w/ the "total_reclaimed" change.
--Ying
Or just stop resetting nr_reclaimed
> each time around the loop.
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-09 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 19:42 Ying Han
2012-04-09 19:50 ` Andrew Morton
2012-04-09 21:23 ` Ying Han [this message]
2012-04-09 22:29 ` Ying Han
2012-04-09 23:24 ` Hugh Dickins
2012-04-10 0:04 ` Andrew Morton
2012-04-10 15:00 ` Hillf Danton
2012-04-10 15:16 ` Hillf Danton
2012-04-10 16:44 ` Ying Han
2012-04-11 11:55 ` Hillf Danton
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='CALWz4ixm+s8tS6cHcpac4MNshB9GiZrpuQO+hjY1rOqEA=o-_w@mail.gmail.com' \
--to=yinghan@google.com \
--cc=akpm@linux-foundation.org \
--cc=dhillf@gmail.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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