From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751157AbdEaM0E convert rfc822-to-8bit (ORCPT ); Wed, 31 May 2017 08:26:04 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:55529 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751078AbdEaM0D (ORCPT ); Wed, 31 May 2017 08:26:03 -0400 Date: Wed, 31 May 2017 15:25:43 +0300 User-Agent: K-9 Mail for Android In-Reply-To: <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> <20170531120533.GK27783@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE To: Michal Hocko CC: Vlastimil Babka , "Kirill A. Shutemov" , Andrew Morton , Arnd Bergmann , "Kirill A. Shutemov" , Andrea Arcangeli , Pavel Emelyanov , linux-mm , lkml , Linux API From: Mike Rapoprt X-TM-AS-GCONF: 00 x-cbid: 17053112-0040-0000-0000-000003BDC8C5 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17053112-0041-0000-0000-000020516214 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-31_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1705310227 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On May 31, 2017 3:05:56 PM GMT+03:00, Michal Hocko wrote: >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? Well, I don't​ know, it's pretty much future telling :) For sure, without the new madvise nobody will be even able to do that.