From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f71.google.com (mail-lf0-f71.google.com [209.85.215.71]) by kanga.kvack.org (Postfix) with ESMTP id AC8826B0253 for ; Tue, 18 Oct 2016 10:32:11 -0400 (EDT) Received: by mail-lf0-f71.google.com with SMTP id n3so13134791lfn.5 for ; Tue, 18 Oct 2016 07:32:11 -0700 (PDT) Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com. [2a00:1450:4010:c07::244]) by mx.google.com with ESMTPS id 35si1908289lfw.12.2016.10.18.07.32.09 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Oct 2016 07:32:09 -0700 (PDT) Received: by mail-lf0-x244.google.com with SMTP id x23so27194291lfi.1 for ; Tue, 18 Oct 2016 07:32:09 -0700 (PDT) Date: Tue, 18 Oct 2016 17:32:07 +0300 From: "Kirill A. Shutemov" Subject: Re: [PATCH] shmem: avoid huge pages for small files Message-ID: <20161018143207.GA5833@node.shutemov.name> References: <20161017121809.189039-1-kirill.shutemov@linux.intel.com> <20161017123021.rlyz44dsf4l4xnve@black.fi.intel.com> <20161017141245.GC27459@dhcp22.suse.cz> <20161017145539.GA26930@node.shutemov.name> <20161018142007.GL12092@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161018142007.GL12092@dhcp22.suse.cz> Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: "Kirill A. Shutemov" , Hugh Dickins , Andrea Arcangeli , Andrew Morton , Andi Kleen , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Tue, Oct 18, 2016 at 04:20:07PM +0200, Michal Hocko wrote: > On Mon 17-10-16 17:55:40, Kirill A. Shutemov wrote: > > On Mon, Oct 17, 2016 at 04:12:46PM +0200, Michal Hocko wrote: > > > On Mon 17-10-16 15:30:21, Kirill A. Shutemov wrote: > [...] > > > > We add two handle to specify minimal file size for huge pages: > > > > > > > > - mount option 'huge_min_size'; > > > > > > > > - sysfs file /sys/kernel/mm/transparent_hugepage/shmem_min_size for > > > > in-kernel tmpfs mountpoint; > > > > > > Could you explain who might like to change the minimum value (other than > > > disable the feautre for the mount point) and for what reason? > > > > Depending on how well CPU microarchitecture deals with huge pages, you > > might need to set it higher in order to balance out overhead with benefit > > of huge pages. > > I am not sure this is a good argument. How do a user know and what will > help to make that decision? Why we cannot autotune that? In other words, > adding new knobs just in case turned out to be a bad idea in the past. Well, I don't see a reasonable way to autotune it. We can just let arch-specific code to redefine it, but the argument below still stands. > > In other case, if it's known in advance that specific mount would be > > populated with large files, you might want to set it to zero to get huge > > pages allocated from the beginning. > > Cannot we use [mf]advise for that purpose? There's no fadvise for this at the moment. We can use madvise, except that the patch makes it lower priority than the limit :P. I'll fix that. But in general, it would require change to the program which is not always desirable or even possible. -- Kirill A. Shutemov -- 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