lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Mon, 6 Nov 2017 18:11:50 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Maxim Levitsky <maximlevitsky@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org
Subject: Re: Guaranteed allocation of huge pages (1G) using movablecore=N
 doesn't seem to work at all

On Mon 06-11-17 19:03:08, Maxim Levitsky wrote:
> I am fully aware of this.
> This is why we have /proc/vm/treat_hugepages_as_moveable which I did set.
> Did you remove this option?

Yes http://lkml.kernel.org/r/20171003072619.8654-1-mhocko@kernel.org

> I don't need/have memory hotplug so I am ok with huge pages beeing not
> movable in the movable zone.
> The idea here is that other pages in that zone should be moveable so I
> should be able to move all of them outside and replace them with hugepages.
> This clearly doesn't work here so thats why I am asking my question

This is an abuse of the zone movable. If we really want gigapages
movable then we should implement that. Maybe it would be as simple as
updating hugepage_migration_supported to support PUD pages. But this
requires some testing.
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists