From: Joonsoo Kim <firstname.lastname@example.org> To: Michal Hocko <email@example.com> Cc: Andrew Morton <firstname.lastname@example.org>, "Kirill A . Shutemov" <email@example.com>, Mel Gorman <firstname.lastname@example.org>, Vlastimil Babka <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: [PATCH] mm/thp: don't count ZONE_MOVABLE as the target for freepage reserving Date: Thu, 5 Apr 2018 17:10:13 +0900 [thread overview] Message-ID: <20180405081013.GB631@js1304-desktop> (raw) In-Reply-To: <20180405080539.GA631@js1304-desktop> On Thu, Apr 05, 2018 at 05:05:39PM +0900, Joonsoo Kim wrote: > 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 <firstname.lastname@example.org> > > > > > > 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. Oops.. s/more/less > > > > 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. > > http://lkml.kernel.org/r/20180102063528.GG30397@yexl-desktop Thanks.
next prev parent reply other threads:[~2018-04-05 8:10 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 2018-04-05 8:10 ` Joonsoo Kim [this message] 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: 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=20180405081013.GB631@js1304-desktop \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] mm/thp: don'\''t count ZONE_MOVABLE as the target for freepage reserving' \ /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
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.