linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ying Han <yinghan@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"minchan.kim@gmail.com" <minchan.kim@gmail.com>,
	"mgorman@suse.de" <mgorman@suse.de>
Subject: Re: [PATCH] fix get_scan_count for working well with small targets
Date: Tue, 26 Apr 2011 10:36:51 -0700	[thread overview]
Message-ID: <BANLkTikACmxYqczKtJjO_FVWCy2=rVjUMA@mail.gmail.com> (raw)
In-Reply-To: <20110426181724.f8cdad57.kamezawa.hiroyu@jp.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 4430 bytes --]

On Tue, Apr 26, 2011 at 2:17 AM, KAMEZAWA Hiroyuki <
kamezawa.hiroyu@jp.fujitsu.com> wrote:

> At memory reclaim, we determine the number of pages to be scanned
> per zone as
>        (anon + file) >> priority.
> Assume
>        scan = (anon + file) >> priority.
>
> If scan < SWAP_CLUSTER_MAX, shlink_list will be skipped for this
> priority and results no-sacn.  This has some problems.
>
>  1. This increases priority as 1 without any scan.
>     To do scan in DEF_PRIORITY always, amount of pages should be larger
> than
>     512M. If pages>>priority < SWAP_CLUSTER_MAX, it's recorded and scan
> will be
>     batched, later. (But we lose 1 priority.)
>     But if the amount of pages is smaller than 16M, no scan at priority==0
>     forever.
>
>  2. If zone->all_unreclaimabe==true, it's scanned only when priority==0.
>     So, x86's ZONE_DMA will never be recoverred until the user of pages
>     frees memory by itself.
>
>  3. With memcg, the limit of memory can be small. When using small memcg,
>     it gets priority < DEF_PRIORITY-2 very easily and need to call
>     wait_iff_congested().
>     For doing scan before priorty=9, 64MB of memory should be used.
>
> This patch tries to scan SWAP_CLUSTER_MAX of pages in force...when
>
>  1. the target is enough small.
>  2. it's kswapd or memcg reclaim.
>
> Then we can avoid rapid priority drop and may be able to recover
> all_unreclaimable in a small zones.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
>  mm/vmscan.c |   31 ++++++++++++++++++++++++++-----
>  1 file changed, 26 insertions(+), 5 deletions(-)
>
> Index: memcg/mm/vmscan.c
> ===================================================================
> --- memcg.orig/mm/vmscan.c
> +++ memcg/mm/vmscan.c
> @@ -1737,6 +1737,16 @@ static void get_scan_count(struct zone *
>        u64 fraction[2], denominator;
>        enum lru_list l;
>        int noswap = 0;
> +       int may_noscan = 0;
> +
> +
>
extra line?


> +       anon  = zone_nr_lru_pages(zone, sc, LRU_ACTIVE_ANON) +
> +               zone_nr_lru_pages(zone, sc, LRU_INACTIVE_ANON);
> +       file  = zone_nr_lru_pages(zone, sc, LRU_ACTIVE_FILE) +
> +               zone_nr_lru_pages(zone, sc, LRU_INACTIVE_FILE);
> +
> +       if (((anon + file) >> priority) < SWAP_CLUSTER_MAX)
> +               may_noscan = 1;
>
>        /* If we have no swap space, do not bother scanning anon pages. */
>        if (!sc->may_swap || (nr_swap_pages <= 0)) {
> @@ -1747,11 +1757,6 @@ static void get_scan_count(struct zone *
>                goto out;
>        }
>
> -       anon  = zone_nr_lru_pages(zone, sc, LRU_ACTIVE_ANON) +
> -               zone_nr_lru_pages(zone, sc, LRU_INACTIVE_ANON);
> -       file  = zone_nr_lru_pages(zone, sc, LRU_ACTIVE_FILE) +
> -               zone_nr_lru_pages(zone, sc, LRU_INACTIVE_FILE);
> -
>        if (scanning_global_lru(sc)) {
>                free  = zone_page_state(zone, NR_FREE_PAGES);
>                /* If we have very few page cache pages,
> @@ -1814,10 +1819,26 @@ out:
>                unsigned long scan;
>
>                scan = zone_nr_lru_pages(zone, sc, l);
> +
>
extra line?

>                if (priority || noswap) {
>                        scan >>= priority;
>                        scan = div64_u64(scan * fraction[file],
> denominator);
>                }
> +
> +               if (!scan &&
> +                   may_noscan &&
> +                   (current_is_kswapd() || !scanning_global_lru(sc))) {
> +                       /*
> +                        * if we do target scan, the whole amount of memory
> +                        * can be too small to scan with low priority
> value.
> +                        * This raise up priority rapidly without any scan.
> +                        * Avoid that and give some scan.
> +                        */
> +                       if (file)
> +                               scan = SWAP_CLUSTER_MAX;
> +                       else if (!noswap && (fraction[anon] >
> fraction[file]*16))
> +                               scan = SWAP_CLUSTER_MAX;
> +               }
>
Ok, so we are changing the global kswapd, and per-memcg bg and direct
reclaim both. Just to be clear here.
Also, how did we calculated the "16" to be the fraction of anon vs file?

               nr[l] = nr_scan_try_batch(scan,
>                                          &reclaim_stat->nr_saved_scan[l]);
>        }
>
> Thank you

--Ying

[-- Attachment #2: Type: text/html, Size: 5618 bytes --]

  reply	other threads:[~2011-04-26 17:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-26  9:17 [PATCH] fix get_scan_count for working well with small targets KAMEZAWA Hiroyuki
2011-04-26 17:36 ` Ying Han [this message]
2011-04-26 23:58   ` KAMEZAWA Hiroyuki
2011-04-26 20:59 ` Andrew Morton
2011-04-26 23:46   ` KAMEZAWA Hiroyuki
2011-04-27  1:50   ` [PATCH v2] " KAMEZAWA Hiroyuki
2011-04-27  3:09     ` KAMEZAWA Hiroyuki
2011-04-27  5:08     ` Minchan Kim
2011-04-27  5:31       ` KAMEZAWA Hiroyuki

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='BANLkTikACmxYqczKtJjO_FVWCy2=rVjUMA@mail.gmail.com' \
    --to=yinghan@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan.kim@gmail.com \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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).