All of
 help / color / mirror / Atom feed
From: Joonsoo Kim <>
To: Michal Hocko <>
Cc: Andrew Morton <>,
	"Kirill A . Shutemov" <>,
	Mel Gorman <>, Vlastimil Babka <>,,
Subject: Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving
Date: Thu, 5 Apr 2018 17:05:39 +0900	[thread overview]
Message-ID: <20180405080539.GA631@js1304-desktop> (raw)
In-Reply-To: <>

On Thu, Apr 05, 2018 at 09:57:53AM +0200, Michal Hocko wrote:
> On Thu 05-04-18 16:27:16, Joonsoo Kim wrote:
> > From: Joonsoo Kim <>
> > 
> > ZONE_MOVABLE only has movable pages so we don't need to keep enough
> > freepages to avoid or deal with fragmentation. So, don't count it.
> > 
> > This changes min_free_kbytes and thus min_watermark greatly
> > if ZONE_MOVABLE is used. It will make the user uses more memory.
> OK, but why does it matter. Has anybody seen this as an issue?

There was a regression report for CMA patchset and I think that it is
related to this problem. CMA patchset makes the system uses one more
zone (ZONE_MOVABLE) and then increase min_free_kbytes. It reduces
usable memory and it could cause regression.


  reply	other threads:[~2018-04-05  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  7:27 js1304
2018-04-05  7:57 ` Michal Hocko
2018-04-05  8:05   ` Joonsoo Kim [this message]
2018-04-05  8:10     ` Joonsoo Kim
2018-04-05  8:27     ` Michal Hocko

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180405080539.GA631@js1304-desktop \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] mm/thp: don'\''t count ZONE_MOVABLE as the target for freepage reserving' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.