From: Mel Gorman <mgorman@techsingularity.net>
To: Shantanu Goel <sgoel01@yahoo.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] vmscan: fix zone balance check in prepare_kswapd_sleep
Date: Tue, 7 Feb 2017 09:54:10 +0000 [thread overview]
Message-ID: <20170207095410.6xflcfktwlofbg3f@techsingularity.net> (raw)
In-Reply-To: <68644e18-ed8d-0559-4ac2-fb3162f6ba67@yahoo.com>
On Mon, Feb 06, 2017 at 07:16:46PM -0500, Shantanu Goel wrote:
> > However, note that there is a slight risk that kswapd will sleep for a
> > short interval early due to a very small zone such as ZONE_DMA. If this
> > is a general problem then it'll manifest as less kswapd reclaim and more
> > direct reclaim. If it turns out this is an issue then a revert will not
> > be the right fix. Instead, all the checks for zone_balance will need to
> > account for the only balanced zone being a tiny percentage of memory in
> > the node.
> >
>
> I see your point. Perhaps we can introduce a constraint that
> ensures the balanced zones constitute say 1/4 or 1/2 of
> memory in the classzone? I believe there used to be such
> a constraint at one time for higher order allocations.
>
There was but it was fairly complex and I'd rather avoid it if at all
possible and certainly not without data backing it up.
--
Mel Gorman
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-07 9:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <719282122.1183240.1486298780546.ref@mail.yahoo.com>
2017-02-05 12:46 ` [PATCH] vmscan: fix zone balance check in prepare_kswapd_sleep Shantanu Goel
2017-02-06 3:19 ` Hillf Danton
2017-02-06 8:31 ` Michal Hocko
2017-02-06 11:51 ` Vlastimil Babka
2017-02-06 16:17 ` Mel Gorman
2017-02-06 17:43 ` Vlastimil Babka
2017-02-06 22:24 ` Mel Gorman
2017-02-07 0:16 ` Shantanu Goel
2017-02-07 9:54 ` Mel Gorman [this message]
2017-02-10 13:11 ` Vlastimil Babka
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=20170207095410.6xflcfktwlofbg3f@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=linux-mm@kvack.org \
--cc=sgoel01@yahoo.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
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).