From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750913AbdE3E0Q (ORCPT ); Tue, 30 May 2017 00:26:16 -0400 Received: from mail-pf0-f172.google.com ([209.85.192.172]:33591 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750811AbdE3E0O (ORCPT ); Tue, 30 May 2017 00:26:14 -0400 Date: Mon, 29 May 2017 21:26:12 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Mike Rapoport cc: Andrew Morton , Arnd Bergmann , "Kirill A. Shutemov" , Andrea Arcangeli , Michal Hocko , Vlastimil Babka , linux-mm , linux-api , lkml Subject: Re: [PATCH v2] mm: introduce MADV_RESET_HUGEPAGE In-Reply-To: <1496035924-27251-1-git-send-email-rppt@linux.vnet.ibm.com> Message-ID: References: <1496035924-27251-1-git-send-email-rppt@linux.vnet.ibm.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > Acked-by: Kirill A. Shutemov 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?