From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Alan Jenkins <alan.christopher.jenkins@gmail.com>,
stable@vger.kernel.org
Subject: [PATCH] mm: fix setting the high and low watermarks
Date: Fri, 21 Jun 2019 12:43:25 +0100 [thread overview]
Message-ID: <20190621114325.711-1-alan.christopher.jenkins@gmail.com> (raw)
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
---
Tested by compiler :-).
Ideally the commit message would be clear about what happens the
*first* time __setup_per_zone_watermarks() is called. I guess that
zone->watermark_boost is *usually* zero, or we would have noticed
some wild problems :-). However I am not familiar with how the zone
structures are allocated & initialized. Maybe there is a case where
zone->watermark_boost could contain an arbitrary unitialized value
at this point. Can we rule that out?
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index c02cff1ed56e..db9758cda6f8 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7606,9 +7606,9 @@ static void __setup_per_zone_wmarks(void)
mult_frac(zone_managed_pages(zone),
watermark_scale_factor, 10000));
+ zone->watermark_boost = 0;
zone->_watermark[WMARK_LOW] = min_wmark_pages(zone) + tmp;
zone->_watermark[WMARK_HIGH] = min_wmark_pages(zone) + tmp * 2;
- zone->watermark_boost = 0;
spin_unlock_irqrestore(&zone->lock, flags);
}
--
2.20.1
next reply other threads:[~2019-06-21 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 11:43 Alan Jenkins [this message]
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 ` [PATCH] mm: fix setting " Mel Gorman
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=20190621114325.711-1-alan.christopher.jenkins@gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--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