From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wj0-f198.google.com (mail-wj0-f198.google.com [209.85.210.198]) by kanga.kvack.org (Postfix) with ESMTP id B59B96B0253 for ; Thu, 26 Jan 2017 10:57:13 -0500 (EST) Received: by mail-wj0-f198.google.com with SMTP id jz4so40682304wjb.5 for ; Thu, 26 Jan 2017 07:57:13 -0800 (PST) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com. [2a00:1450:400c:c09::242]) by mx.google.com with ESMTPS id e1si2484207wrd.138.2017.01.26.07.57.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Jan 2017 07:57:12 -0800 (PST) Received: by mail-wm0-x242.google.com with SMTP id r144so51352853wme.0 for ; Thu, 26 Jan 2017 07:57:12 -0800 (PST) Date: Thu, 26 Jan 2017 18:57:09 +0300 From: "Kirill A. Shutemov" Subject: Re: [PATCHv6 06/37] thp: handle write-protection faults for file THP Message-ID: <20170126155709.GA11239@node.shutemov.name> References: <20170126115819.58875-1-kirill.shutemov@linux.intel.com> <20170126115819.58875-7-kirill.shutemov@linux.intel.com> <20170126154439.GB20495@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170126154439.GB20495@bombadil.infradead.org> Sender: owner-linux-mm@kvack.org List-ID: To: Matthew Wilcox Cc: "Kirill A. Shutemov" , Theodore Ts'o , Andreas Dilger , Jan Kara , Andrew Morton , Alexander Viro , Hugh Dickins , Andrea Arcangeli , Dave Hansen , Vlastimil Babka , Ross Zwisler , linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-block@vger.kernel.org On Thu, Jan 26, 2017 at 07:44:39AM -0800, Matthew Wilcox wrote: > On Thu, Jan 26, 2017 at 02:57:48PM +0300, Kirill A. Shutemov wrote: > > For filesystems that wants to be write-notified (has mkwrite), we will > > encount write-protection faults for huge PMDs in shared mappings. > > > > The easiest way to handle them is to clear the PMD and let it refault as > > wriable. > > ... of course, the filesystem could implement ->pmd_fault, and then it > wouldn't hit this case ... I would rather get rid of ->pmd_fault/->huge_fault :) ->fault should be flexible enough to provide for all of them... -- 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