Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752115AbcDQAqc (ORCPT ); Sat, 16 Apr 2016 20:46:32 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:38867 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751811AbcDQAqa (ORCPT ); Sat, 16 Apr 2016 20:46:30 -0400 Date: Sun, 17 Apr 2016 03:46:26 +0300 From: "Kirill A. Shutemov" To: Hugh Dickins Cc: Andrew Morton , "Kirill A. Shutemov" , Andrea Arcangeli , Andres Lagar-Cavilla , Yang Shi , Ning Qu , Stephen Rothwell , kernel test robot , Xiong Zhou , Matthew Wilcox , Greg Thelen , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH mmotm 5/5] huge tmpfs: add shmem_pmd_fault() Message-ID: <20160417004626.GA5169@node.shutemov.name> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1508 Lines: 29 On Sat, Apr 16, 2016 at 04:41:33PM -0700, Hugh Dickins wrote: > The pmd_fault() method gives the filesystem an opportunity to place > a trans huge pmd entry at *pmd, before any pagetable is exposed (and > an opportunity to split it on COW fault): now use it for huge tmpfs. > > This patch is a little raw: with more time before LSF/MM, I would > probably want to dress it up better - the shmem_mapping() calls look > a bit ugly; it's odd to want FAULT_FLAG_MAY_HUGE and VM_FAULT_HUGE just > for a private conversation between shmem_fault() and shmem_pmd_fault(); > and there might be a better distribution of work between those two, but > prising apart that series of huge tests is not to be done in a hurry. > > Good for now, presents the new way, but might be improved later. > > This patch still leaves the huge tmpfs map_team_by_pmd() allocating a > pagetable while holding page lock, but other filesystems are no longer > doing so; and we've not yet settled whether huge tmpfs should (like anon > THP) or should not (like DAX) participate in deposit/withdraw protocol. > > Signed-off-by: Hugh Dickins Just for record: I don't like ->pmd_fault() approach because it results in two requests to file system (two shmem_fault() in this case) if we don't have a huge page to map: one for huge page (failed) and then one for small. I think this case should be rather common: all mounts without huge pages enabled. I expect performance regression from this too. -- Kirill A. Shutemov