[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1705292125210.9353@chino.kir.corp.google.com>
Date: Mon, 29 May 2017 21:26:12 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Mike Rapoport <rppt@...ux.vnet.ibm.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Arnd Bergmann <arnd@...db.de>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Michal Hocko <mhocko@...nel.org>,
Vlastimil Babka <vbabka@...e.cz>,
linux-mm <linux-mm@...ck.org>,
linux-api <linux-api@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] mm: introduce MADV_RESET_HUGEPAGE
On Mon, 29 May 2017, Mike Rapoport wrote:
> Currently applications can explicitly enable or disable THP for a memory
> region using MADV_HUGEPAGE or MADV_NOHUGEPAGE. However, once either of
> these advises is used, the region will always have
> VM_HUGEPAGE/VM_NOHUGEPAGE flag set in vma->vm_flags.
> The MADV_RESET_HUGEPAGE resets both these flags and allows managing THP in
> the region according to system-wide settings.
>
> Signed-off-by: Mike Rapoport <rppt@...ux.vnet.ibm.com>
> Acked-by: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
I feel like we may be losing some information from the v1 thread regarding
the usecase. Would it be possible to add something to the changelog to
describe what will use this?
Powered by blists - more mailing lists