From: Michal Hocko <mhocko@suse.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>, linux-mm@kvack.org
Subject: Re: Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all
Date: Tue, 7 Nov 2017 09:30:42 +0100 [thread overview]
Message-ID: <20171107083042.5lnmsz237ccbituj@dhcp22.suse.cz> (raw)
In-Reply-To: <c6ab988b-f95f-3881-a35c-7727292fd44a@suse.cz>
On Tue 07-11-17 09:20:47, Vlastimil Babka wrote:
> On 11/06/2017 07:32 PM, Michal Hocko wrote:
> > On Mon 06-11-17 20:13:36, Maxim Levitsky wrote:
> >> Yes, I tested git head from mainline and few kernels from ubuntu repos
> >> since I was lazy to compile them too.
> >
> > OK, so this hasn't worked realiably as I've suspected.
> >
> >> Do you have an idea what can I do about this issue? Do you think its
> >> feasable to fix this?
> >
> > Well, I think that giga pages need quite some love to be usable
> > reliably. The current implementation is more towards "make it work if
> > there is enough unused memory".
> >
> >> And if not using moveable zone, how would it even be possible to have
> >> guaranreed allocation of 1g pages
> >
> > Having a guaranteed giga pages is something the kernel is not yet ready
> > to offer. Abusing zone movable might look like the right direction
> > but that is not really the case until we make sure those pages are
> > migratable.
>
> Migratable where? It's very unlikely you will be able to migrate them
> away from a movable zone to a normal zone. So the use case is migration
> between hotplugable nodes, so one of them can be removed?
Yes, basically what we do for hugetlb pages normally. Smaller hugetlb
pages are more likely to succeed, though.
> That would
> probably be an improvement (even if you could not guarantee to offline
> all hotplugable nodes at once without admin intervention removing those
> giga pages). Right now the only scenario where giga pages are compatible
> with hot-remove is to put them on the already-limited non-removable node
> 0...
Yes, we will never be perfect, but I can see why people want to allocate
from movable zones so we definitely should work on making giga pages
more robust. The current state makes cry...
--
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-11-07 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 9:55 Guaranteed allocation of huge pages (1G) using movablecore=N doesn't seem to work at all Maxim Levitsky
2017-11-06 13:05 ` Michal Hocko
2017-11-06 17:03 ` Maxim Levitsky
2017-11-06 17:11 ` Michal Hocko
[not found] ` <CACAwPwZuiT9BfunVgy73KYjGfVopgcE0dknAxSLPNeJB8rkcMQ@mail.gmail.com>
[not found] ` <CACAwPwZqFRyFJhb7pyyrufah+1TfCDuzQMo3qwJuMKkp6aYd_Q@mail.gmail.com>
[not found] ` <CACAwPwbA0NpTC9bfV7ySHkxPrbZJVvjH=Be5_c25Q3S8qNay+w@mail.gmail.com>
[not found] ` <CACAwPwamD4RL9O8wujK_jCKGu=x0dBBmH9O-9078cUEEk4WsMA@mail.gmail.com>
[not found] ` <CACAwPwYKjK5RT-ChQqqUnD7PrtpXg1WhTHGK3q60i6StvDMDRg@mail.gmail.com>
[not found] ` <CACAwPwav-eY4_nt=Z7TQB8WMFg+1X5WY2Gkgxph74X7=Ovfvrw@mail.gmail.com>
[not found] ` <CACAwPwaP05FgxTp=kavwgFZF+LEGO-OSspJ4jH+Y=_uRxiVZaA@mail.gmail.com>
[not found] ` <CACAwPwY5ss_D9kj7XoLVVkQ9=KXDFCnyDzdoxkGxhJZBNFre3w@mail.gmail.com>
2017-11-06 17:36 ` Maxim Levitsky
2017-11-06 18:04 ` Michal Hocko
2017-11-06 18:13 ` Maxim Levitsky
2017-11-06 18:32 ` Michal Hocko
2017-11-06 19:31 ` Michal Hocko
2017-11-06 22:32 ` Maxim Levitsky
2017-11-07 8:20 ` Vlastimil Babka
2017-11-07 8:30 ` 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=20171107083042.5lnmsz237ccbituj@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=linux-mm@kvack.org \
--cc=maximlevitsky@gmail.com \
--cc=vbabka@suse.cz \
/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).