linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
	mgorman@techsingularity.net, osalvador@suse.de
Subject: Re: [PATCH] mm, page_alloc: clear zone_movable_pfn if the node doesn't have ZONE_MOVABLE
Date: Wed, 19 Dec 2018 07:56:25 +0100	[thread overview]
Message-ID: <20181219065625.GC10480@dhcp22.suse.cz> (raw)
In-Reply-To: <20181218202743.i5wvlzipzdl54fuq@master>

On Tue 18-12-18 20:27:43, Wei Yang wrote:
[...]
> BTW, would this eat lower zone's memory? For example, has less DMA32?

Yes I think so. If the distribution should be even and some node(s) span
only lower 32b address range then there is no other option than shrink
the DMA32 zone. There is a note
			In the
			event, a node is too small to have both ZONE_NORMAL and
			ZONE_MOVABLE, kernelcore memory will take priority and
			other nodes will have a larger ZONE_MOVABLE.
which explains that this might not be the case though.

Btw. I have to say I quite do not like this interface not to mention the
implementation. THere are users to rely on it though so we cannot remove
it. There is a lot of room for cleanups there.
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2018-12-19  6:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 12:56 Wei Yang
2018-12-17 10:25 ` Michal Hocko
2018-12-17 14:18   ` Wei Yang
2018-12-18 12:14     ` Michal Hocko
2018-12-18 14:39       ` Wei Yang
2018-12-18 14:47         ` Michal Hocko
2018-12-18 20:27           ` Wei Yang
2018-12-19  6:56             ` Michal Hocko [this message]
2018-12-19 12:56               ` Wei Yang

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=20181219065625.GC10480@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=osalvador@suse.de \
    --cc=richard.weiyang@gmail.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