From: Minchan Kim <minchan.kim@gmail.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>, "Rafael J. Wysocki" <rjw@sisk.pl>,
"M. Vefa Bicakci" <bicave@superonline.com>,
stable@kernel.org
Subject: Re: [PATCH] vmscan: check all_unreclaimable in direct reclaim path
Date: Mon, 13 Sep 2010 01:20:56 +0900 [thread overview]
Message-ID: <AANLkTimzidMtKs073bxrYz8GsenRNuAAnQMy7a=FS5Sf@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=4kwu0Y5-MDye3TD+zZiku62NtNCMtWLn==p12@mail.gmail.com>
Thanks, Dave.
On Fri, Sep 10, 2010 at 5:24 PM, Dave Young <hidave.darkstar@gmail.com> wrote:
> On Thu, Sep 9, 2010 at 6:19 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
>> On Thu, 9 Sep 2010 00:45:27 +0900
>> Minchan Kim <minchan.kim@gmail.com> wrote:
>>
>>> +static inline bool zone_reclaimable(struct zone *zone)
>>> +{
>>> + return zone->pages_scanned < zone_reclaimable_pages(zone) * 6;
>>> +}
>>> +
>>> +static inline bool all_unreclaimable(struct zonelist *zonelist,
>>> + struct scan_control *sc)
>>> +{
>>> + struct zoneref *z;
>>> + struct zone *zone;
>>> + bool all_unreclaimable = true;
>>> +
>>> + if (!scanning_global_lru(sc))
>>> + return false;
>>> +
>>> + for_each_zone_zonelist_nodemask(zone, z, zonelist,
>>> + gfp_zone(sc->gfp_mask), sc->nodemask) {
>>> + if (!populated_zone(zone))
>>> + continue;
>>> + if (!cpuset_zone_allowed_hardwall(zone, GFP_KERNEL))
>>> + continue;
>>> + if (zone_reclaimable(zone)) {
>>> + all_unreclaimable = false;
>>> + break;
>>> + }
>>> + }
>>> +
>>> return all_unreclaimable;
>>> }
>>
>> Could we have some comments over these functions please? Why they
>> exist, what problem they solve, how they solve them, etc. Stuff which
>> will be needed for maintaining this code three years from now.
>>
>> We may as well remove the `inline's too. gcc will tkae care of that.
>>
>>> - if (nr_slab == 0 &&
>>> - zone->pages_scanned >= (zone_reclaimable_pages(zone) * 6))
>>> + if (nr_slab == 0 && !zone_reclaimable(zone))
>>
>> Extra marks for working out and documenting how we decided on the value
>> of "6". Sigh. It's hopefully in the git record somewhere.
>
> Here it is (necessary to add additional comment?):
>
> commit 4ff1ffb4870b007b86f21e5f27eeb11498c4c077
> Author: Nick Piggin <npiggin@suse.de>
> Date: Mon Sep 25 23:31:28 2006 -0700
>
> [PATCH] oom: reclaim_mapped on oom
>
> Potentially it takes several scans of the lru lists before we can even start
> reclaiming pages.
>
> mapped pages, with young ptes can take 2 passes on the active list + one on
> the inactive list. But reclaim_mapped may not always kick in
> instantly, so it
> could take even more than that.
>
> Raise the threshold for marking a zone as all_unreclaimable from a
> factor of 4
> time the pages in the zone to 6. Introduce a mechanism to force
> reclaim_mapped if we've reached a factor 3 and still haven't made progress.
>
> Previously, a customer doing stress testing was able to easily OOM the box
> after using only a small fraction of its swap (~100MB). After the
> patches, it
> would only OOM after having used up all swap (~800MB).
>
>>
>> --
>> 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/ .
>> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>>
>>
>
>
>
> --
> Regards
> dave
>
--
Kind regards,
Minchan Kim
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-09-12 16:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 14:40 Minchan Kim
2010-09-05 22:30 ` Rafael J. Wysocki
2010-09-08 5:48 ` Johannes Weiner
2010-09-08 15:45 ` Minchan Kim
2010-09-08 22:19 ` Andrew Morton
2010-09-10 8:24 ` Dave Young
2010-09-12 16:20 ` Minchan Kim [this message]
2010-09-12 16:20 ` Minchan Kim
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='AANLkTimzidMtKs073bxrYz8GsenRNuAAnQMy7a=FS5Sf@mail.gmail.com' \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bicave@superonline.com \
--cc=hannes@cmpxchg.org \
--cc=hidave.darkstar@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=rjw@sisk.pl \
--cc=stable@kernel.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