On Tue 03-10-17 09:49:01, Alexandru Moise wrote:
> On Tue, Oct 03, 2017 at 09:33:01AM +0200, Michal Hocko wrote:
> > I am sorry to jump here late
> >
> > On Thu 28-09-17 14:43:24, Andrew Morton wrote:
> > > From: Alexandru Moise <00moses.alexander00@xxxxxxxxx>
> > > Subject: mm/madvise: enable soft offline of HugeTLB pages at PUD level
> > >
> > > Since 94310cbcaa3c2 ("mm/madvise: enable (soft|hard) offline of HugeTLB
> > > pages at PGD level") we've been able to soft offline 1G hugepages at the
> > > PGD level, however x86_64 gigantic hugepages are at the PUD level so we
> > > should add an extra check to account for hstate order at PUD level.
> > >
> > > I'm not sure if this also applies to 5 level page tables on x86_64
> > > however. Tested with 4 level pagetable.
> >
> > This patch is wrong I believe! And I suspect 94310cbcaa3c2 is wrong as
> > well but I am not familiar with ppc enough to be sure. It will allow
> > PUD, PGD pages to be allocated from the zone movable while at least PUD
> > pages are not migrateable for x86_64 AFAIR. Are PGD pages migrateable
> > on ppc? If yes, are there any other architectures to allow PGD hugetlb
> > pages which are not migrateable?
> >
> > Andrew, could you drop it please?
> >
>
> What exactly makes it wrong? When I tested this I saw no failure,
> copy_huge_page() seems to take into account gigantic hugepages,
> and when you move the mapping you don't really care about the
> page size?
Migrating 1GB (PUD) pages on x86_64 is just too easy to fail (if it
works at all) and so such an allocation can easily prefent memory
offline to succeed. Have you tested that scenario?
Btw. (ab)using hugepage_migration_supported for HWpoinsoning sounds
wrong to me. You do not need movable zone for the functionality.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
