From: Mel Gorman <mgorman@techsingularity.net>
To: Alan Jenkins <alan.christopher.jenkins@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mm: fix setting the high and low watermarks
Date: Fri, 21 Jun 2019 15:16:33 +0100 [thread overview]
Message-ID: <20190621141633.GA2978@techsingularity.net> (raw)
In-Reply-To: <20190621114325.711-1-alan.christopher.jenkins@gmail.com>
On Fri, Jun 21, 2019 at 12:43:25PM +0100, Alan Jenkins wrote:
> When setting the low and high watermarks we use min_wmark_pages(zone).
> I guess this is to reduce the line length. But we forgot that this macro
> includes zone->watermark_boost. We need to reset zone->watermark_boost
> first. Otherwise the watermarks will be set inconsistently.
>
> E.g. this could cause inconsistent values if the watermarks have been
> boosted, and then you change a sysctl which triggers
> __setup_per_zone_wmarks().
>
> I strongly suspect this explains why I have seen slightly high watermarks.
> Suspicious-looking zoneinfo below - notice high-low != low-min.
>
> Node 0, zone Normal
> pages free 74597
> min 9582
> low 34505
> high 36900
>
> https://unix.stackexchange.com/questions/525674/my-low-and-high-watermarks-seem-higher-than-predicted-by-documentation-sysctl-vm/525687
>
> Signed-off-by: Alan Jenkins <alan.christopher.jenkins@gmail.com>
> Fixes: 1c30844d2dfe ("mm: reclaim small amounts of memory when an external
> fragmentation event occurs")
> Cc: stable@vger.kernel.org
Either way
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2019-06-21 14:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:43 Alan Jenkins
2019-06-21 12:09 ` Vlastimil Babka
2019-06-21 14:07 ` Bharath Vedartham
2019-06-24 5:46 ` Vlastimil Babka
2019-06-21 15:31 ` [PATCH v2] mm: avoid inconsistent "boosts" when updating " Alan Jenkins
2019-06-21 20:58 ` David Rientjes
2019-06-21 14:16 ` Mel Gorman [this message]
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=20190621141633.GA2978@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=alan.christopher.jenkins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.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