From: Johannes Weiner <hannes@cmpxchg.org> To: Suren Baghdasaryan <surenb@google.com> Cc: Andrew Morton <akpm@linux-foundation.org>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Shakeel Butt <shakeelb@google.com>, Rik van Riel <riel@surriel.com>, Michal Hocko <mhocko@suse.com>, linux-mm <linux-mm@kvack.org>, cgroups mailinglist <cgroups@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>, kernel-team@fb.com Subject: Re: [PATCH 3/3] mm: vmscan: enforce inactive:active ratio at the reclaim root Date: Tue, 12 Nov 2019 13:00:19 -0500 Message-ID: <20191112180019.GB178331@cmpxchg.org> (raw) In-Reply-To: <CAJuCfpHSTr8Vt+Tj-Hj4OBYHq1ucw7_B1VoVWKEHQVPHaMhUdA@mail.gmail.com> On Sun, Nov 10, 2019 at 06:15:50PM -0800, Suren Baghdasaryan wrote: > On Thu, Nov 7, 2019 at 12:53 PM Johannes Weiner <hannes@cmpxchg.org> wrote: > > @@ -2758,7 +2775,17 @@ static bool shrink_node(pg_data_t *pgdat, struct scan_control *sc) > > total_high_wmark += high_wmark_pages(zone); > > } > > > > - sc->file_is_tiny = file + free <= total_high_wmark; > > + /* > > + * Consider anon: if that's low too, this isn't a > > + * runaway file reclaim problem, but rather just > > + * extreme pressure. Reclaim as per usual then. > > + */ > > + anon = node_page_state(pgdat, NR_INACTIVE_ANON); > > + > > + sc->file_is_tiny = > > + file + free <= total_high_wmark && > > + !(sc->may_deactivate & DEACTIVATE_ANON) && > > + anon >> sc->priority; > > The name of file_is_tiny flag seems to not correspond with its actual > semantics anymore. Maybe rename it into "skip_file"? I'm not a fan of file_is_tiny, but I also don't like skip_file. IMO it's better to have it describe a situation instead of an action, in case we later want to take additional action for that situation. Any other ideas? ;) > I'm confused about why !(sc->may_deactivate & DEACTIVATE_ANON) should > be a prerequisite for skipping file LRU reclaim. IIUC this means we > will skip reclaiming from file LRU only when anonymous page > deactivation is not allowed. Could you please add a comment explaining > this? The comment above this check tries to explain it: the definition of file being "tiny" is dependent on the availability of anon. It's a relative comparison. If file only has a few pages, and anon is easily reclaimable (does not require deactivation to reclaim pages), then file is "tiny" and we should go after the more plentiful anon pages. If anon is under duress, too, this preference doesn't make sense and we should just reclaim both lists equally, as per usual. Note that I'm not introducing this constraint, I'm just changing how it's implemented. From the patch: > > /* > > * If the system is almost out of file pages, force-scan anon. > > - * But only if there are enough inactive anonymous pages on > > - * the LRU. Otherwise, the small LRU gets thrashed. > > */ > > - if (sc->file_is_tiny && > > - !inactive_list_is_low(lruvec, false, sc, false) && > > - lruvec_lru_size(lruvec, LRU_INACTIVE_ANON, > > - sc->reclaim_idx) >> sc->priority) { > > + if (sc->file_is_tiny) { > > scan_balance = SCAN_ANON; > > goto out; > > } So it's always been checking whether reclaim would deactivate anon, and whether inactive_anon has sufficient pages for this priority.
next prev parent reply index Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-07 20:53 [PATCH 0/3] mm: fix page aging across multiple cgroups Johannes Weiner 2019-11-07 20:53 ` [PATCH 1/3] mm: vmscan: move file exhaustion detection to the node level Johannes Weiner 2019-11-10 22:02 ` Suren Baghdasaryan 2019-11-10 22:09 ` Khadarnimcaan Khadarnimcaan 2019-11-07 20:53 ` [PATCH 2/3] mm: vmscan: detect file thrashing at the reclaim root Johannes Weiner 2019-11-11 2:01 ` Suren Baghdasaryan 2019-11-12 17:45 ` Johannes Weiner 2019-11-12 18:45 ` Suren Baghdasaryan 2019-11-12 18:59 ` Johannes Weiner 2019-11-12 20:35 ` Suren Baghdasaryan 2019-11-14 23:47 ` Shakeel Butt 2019-11-15 16:07 ` Johannes Weiner 2019-11-15 16:52 ` Shakeel Butt 2019-11-07 20:53 ` [PATCH 3/3] mm: vmscan: enforce inactive:active ratio " Johannes Weiner 2019-11-11 2:15 ` Suren Baghdasaryan 2019-11-12 18:00 ` Johannes Weiner [this message] 2019-11-12 19:13 ` Suren Baghdasaryan 2019-11-12 20:34 ` Suren Baghdasaryan 2019-11-15 0:29 ` Shakeel Butt 2019-11-27 22:16 ` Shakeel Butt
Reply instructions: You may reply publically 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=20191112180019.GB178331@cmpxchg.org \ --to=hannes@cmpxchg.org \ --cc=akpm@linux-foundation.org \ --cc=aryabinin@virtuozzo.com \ --cc=cgroups@vger.kernel.org \ --cc=kernel-team@fb.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.com \ --cc=riel@surriel.com \ --cc=shakeelb@google.com \ --cc=surenb@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
Linux-mm Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-mm/0 linux-mm/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-mm linux-mm/ https://lore.kernel.org/linux-mm \ linux-mm@kvack.org public-inbox-index linux-mm Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kvack.linux-mm AGPL code for this site: git clone https://public-inbox.org/public-inbox.git