From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Hocko Subject: Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE Date: Wed, 31 May 2017 14:05:56 +0200 Message-ID: <20170531120533.GK27783@dhcp22.suse.cz> References: <20170524075043.GB3063@rapoport-lnx> <20170524103947.GC3063@rapoport-lnx> <20170524111800.GD14733@dhcp22.suse.cz> <20170524142735.GF3063@rapoport-lnx> <20170530074408.GA7969@dhcp22.suse.cz> <20170530101921.GA25738@rapoport-lnx> <20170530103930.GB7969@dhcp22.suse.cz> <20170531090844.GA25375@rapoport-lnx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20170531090844.GA25375@rapoport-lnx> Sender: owner-linux-mm@kvack.org To: Mike Rapoport Cc: Vlastimil Babka , "Kirill A. Shutemov" , Andrew Morton , Arnd Bergmann , "Kirill A. Shutemov" , Andrea Arcangeli , Pavel Emelyanov , linux-mm , lkml , Linux API List-Id: linux-api@vger.kernel.org On Wed 31-05-17 12:08:45, Mike Rapoport wrote: > On Tue, May 30, 2017 at 12:39:30PM +0200, Michal Hocko wrote: [...] > > Also do you expect somebody else would use new madvise? What would be the > > usecase? > > I can think of an application that wants to keep 4K pages to save physical > memory for certain phase, e.g. until these pages are populated with very > few data. After the memory usage increases, the application may wish to > stop preventing khugepged from merging these pages, but it does not have > strong inclination to force use of huge pages. Well, is actually anybody going to do that? -- 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: email@kvack.org