From: Michal Hocko <mhocko@kernel.org>
To: Alexandru Moise <00moses.alexander00@gmail.com>
Cc: corbet@lwn.net, paulmck@linux.vnet.ibm.com,
akpm@linux-foundation.org, tglx@linutronix.de, mingo@kernel.org,
cdall@linaro.org, mchehab@kernel.org, zohar@linux.vnet.ibm.com,
marc.zyngier@arm.com, rientjes@google.com, hannes@cmpxchg.org,
mike.kravetz@oracle.com, n-horiguchi@ah.jp.nec.com,
aneesh.kumar@linux.vnet.ibm.com, punit.agrawal@arm.com,
aarcange@redhat.com, gerald.schaefer@de.ibm.com,
jglisse@redhat.com, kirill.shutemov@linux.intel.com,
will.deacon@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages
Date: Tue, 3 Oct 2017 09:10:19 +0200 [thread overview]
Message-ID: <20171003071019.hdcdjwjabld4el4p@dhcp22.suse.cz> (raw)
In-Reply-To: <20171003054224.GA5025@gmail.com>
On Tue 03-10-17 07:42:25, Alexandru Moise wrote:
> On Mon, Oct 02, 2017 at 06:15:00PM +0200, Michal Hocko wrote:
[...]
> > I really fail to see why kernel vs. movable zones play any role here.
> > Zones should be mostly an implementation detail which userspace
> > shouldn't really care about.
>
> Ok, the whole zone approach is a bad idea. Do you think that there's
> any value at all to trying to make hugepages un-movable at all?
I am not aware of any usecase, to be honest.
> Should
> the hugepages_treat_as_movable sysctl die and just make hugepages movable
> by default?
I think that hugepages_treat_as_movable is just a historical relict from
the time when hugetlb pages were not movable but the main purpose of
the movable zone was different back at the time. Just to clarifiy, the
original intention of the zone was to prevent memory fragmentation and
as hugetlb pages are not fragmenting memory because they are long lived
and contiguous, it was acceptable to use the zone. The purpose of the
zone has changed towards a migratability guarantee since then but the
knob has stayed behind. I think we should just remove it.
--
Michal Hocko
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>
prev parent reply other threads:[~2017-10-03 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 22:51 Alexandru Moise
2017-10-02 12:54 ` Michal Hocko
2017-10-02 14:06 ` Alexandru Moise
2017-10-02 14:27 ` Michal Hocko
2017-10-02 15:06 ` Alexandru Moise
2017-10-02 16:15 ` Michal Hocko
2017-10-03 5:42 ` Alexandru Moise
2017-10-03 7:10 ` Michal Hocko [this message]
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=20171003071019.hdcdjwjabld4el4p@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=00moses.alexander00@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cdall@linaro.org \
--cc=corbet@lwn.net \
--cc=gerald.schaefer@de.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marc.zyngier@arm.com \
--cc=mchehab@kernel.org \
--cc=mike.kravetz@oracle.com \
--cc=mingo@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=punit.agrawal@arm.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=zohar@linux.vnet.ibm.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