From: Greg Thelen <gthelen@google.com>
To: ikalvachev@gmail.com
Cc: Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: fix kswap excessive pressure after wrong condition transfer
Date: Thu, 31 May 2018 12:51:42 -0700 [thread overview]
Message-ID: <CAHH2K0afVpVyMw+_J48pg9ngj9oovBEPBFd3kfCcCfyV7xxF0w@mail.gmail.com> (raw)
In-Reply-To: <20180531193420.26087-1-ikalvachev@gmail.com>
On Thu, May 31, 2018 at 12:34 PM Ivan Kalvachev <ikalvachev@gmail.com> wrote:
>
> Fixes commit 69d763fc6d3aee787a3e8c8c35092b4f4960fa5d
> (mm: pin address_space before dereferencing it while isolating an LRU page)
>
> working code:
>
> mapping = page_mapping(page);
> if (mapping && !mapping->a_ops->migratepage)
> return ret;
>
> buggy code:
>
> if (!trylock_page(page))
> return ret;
>
> mapping = page_mapping(page);
> migrate_dirty = mapping && mapping->a_ops->migratepage;
> unlock_page(page);
> if (!migrate_dirty)
> return ret;
>
> The problem is that !(a && b) = (!a || !b) while the old code was (a && !b).
> The commit message of the buggy commit explains the need for locking/unlocking
> around the check but does not give any reason for the change of the condition.
> It seems to be an unintended change.
>
> The result of that change is noticeable under swap pressure.
> Big memory consumers like browsers would have a lot of pages swapped out,
> even pages that are been used actively, causing the process to repeatedly
> block for second or longer. At the same time there would be gigabytes of
> unused free memory (sometimes half of the total RAM).
> The buffers/cache would also be at minimum size.
>
> Fixes: 69d763fc6d3a ("mm: pin address_space before dereferencing it while isolating an LRU page")
> Signed-off-by: Ivan Kalvachev <ikalvachev@gmail.com>
> ---
> mm/vmscan.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 9b697323a88c..83df26078d13 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -1418,9 +1418,9 @@ int __isolate_lru_page(struct page *page, isolate_mode_t mode)
> return ret;
>
> mapping = page_mapping(page);
> - migrate_dirty = mapping && mapping->a_ops->migratepage;
> + migrate_dirty = mapping && !mapping->a_ops->migratepage;
> unlock_page(page);
> - if (!migrate_dirty)
> + if (migrate_dirty)
> return ret;
> }
> }
> --
> 2.17.1
This looks like yesterday's https://lkml.org/lkml/2018/5/30/1158
next prev parent reply other threads:[~2018-05-31 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 19:34 Ivan Kalvachev
2018-05-31 19:51 ` Greg Thelen [this message]
2018-05-31 21:39 ` Ivan Kalvachev
2018-05-31 23:30 ` Hugh Dickins
2018-06-01 8:49 ` Vlastimil Babka
2018-06-11 15:38 ` Ivan Kalvachev
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=CAHH2K0afVpVyMw+_J48pg9ngj9oovBEPBFd3kfCcCfyV7xxF0w@mail.gmail.com \
--to=gthelen@google.com \
--cc=ikalvachev@gmail.com \
--cc=linux-mm@kvack.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