From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f198.google.com (mail-pf0-f198.google.com [209.85.192.198]) by kanga.kvack.org (Postfix) with ESMTP id DF9A0831F5 for ; Mon, 22 May 2017 13:51:19 -0400 (EDT) Received: by mail-pf0-f198.google.com with SMTP id c10so136376596pfg.10 for ; Mon, 22 May 2017 10:51:19 -0700 (PDT) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com. [148.163.156.1]) by mx.google.com with ESMTPS id 191si15770999pge.30.2017.05.22.10.51.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 22 May 2017 10:51:19 -0700 (PDT) Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v4MHmgQu064563 for ; Mon, 22 May 2017 13:51:18 -0400 Received: from e06smtp11.uk.ibm.com (e06smtp11.uk.ibm.com [195.75.94.107]) by mx0a-001b2d01.pphosted.com with ESMTP id 2am3rw23kd-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Mon, 22 May 2017 13:51:18 -0400 Received: from localhost by e06smtp11.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 22 May 2017 18:51:15 +0100 Date: Mon, 22 May 2017 20:51:07 +0300 From: Mike Rapoport Subject: Re: [PATCH] mm: introduce MADV_CLR_HUGEPAGE References: <1495433562-26625-1-git-send-email-rppt@linux.vnet.ibm.com> <20170522114243.2wrdbncilozygbpl@node.shutemov.name> <20170522133559.GE27382@rapoport-lnx> <20170522135548.GA8514@dhcp22.suse.cz> <20170522142927.GG27382@rapoport-lnx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Message-Id: <20170522175106.GA15644@rapoport-lnx> Sender: owner-linux-mm@kvack.org List-ID: To: Vlastimil Babka Cc: Michal Hocko , "Kirill A. Shutemov" , Andrew Morton , Arnd Bergmann , "Kirill A. Shutemov" , Andrea Arcangeli , Pavel Emelyanov , linux-mm , lkml On Mon, May 22, 2017 at 05:52:47PM +0200, Vlastimil Babka wrote: > On 05/22/2017 04:29 PM, Mike Rapoport wrote: > > On Mon, May 22, 2017 at 03:55:48PM +0200, Michal Hocko wrote: > >> On Mon 22-05-17 16:36:00, Mike Rapoport wrote: > >>> On Mon, May 22, 2017 at 02:42:43PM +0300, Kirill A. Shutemov wrote: > >>>> On Mon, May 22, 2017 at 09:12:42AM +0300, Mike Rapoport wrote: > >>>>> Currently applications can explicitly enable or disable THP for a memory > >>>>> region using MADV_HUGEPAGE or MADV_NOHUGEPAGE. However, once either of > >>>>> these advises is used, the region will always have > >>>>> VM_HUGEPAGE/VM_NOHUGEPAGE flag set in vma->vm_flags. > >>>>> The MADV_CLR_HUGEPAGE resets both these flags and allows managing THP in > >>>>> the region according to system-wide settings. > >>>> > >>>> Seems reasonable. But could you describe an use-case when it's useful in > >>>> real world. > >>> > >>> My use-case was combination of pre- and post-copy migration of containers > >>> with CRIU. > >>> In this case we populate a part of a memory region with data that was saved > >>> during the pre-copy stage. Afterwards, the region is registered with > >>> userfaultfd and we expect to get page faults for the parts of the region > >>> that were not yet populated. However, khugepaged collapses the pages and > >>> the page faults we would expect do not occur. > >> > >> I am not sure I undestand the problem. Do I get it right that the > >> khugepaged will effectivelly corrupt the memory by collapsing a range > >> which is not yet fully populated? If yes shouldn't that be fixed in > >> khugepaged rather than adding yet another madvise command? Also how do > >> you prevent on races? (say you VM_NOHUGEPAGE, khugepaged would be in the > >> middle of the operation and sees a collapsable vma and you get the same > >> result) > > > > Probably I didn't explained it too well. > > > > The range is intentionally not populated. When we combine pre- and > > post-copy for process migration, we create memory pre-dump without stopping > > the process, then we freeze the process without dumping the pages it has > > dirtied between pre-dump and freeze, and then, during restore, we populate > > the dirtied pages using userfaultfd. > > > > When CRIU restores a process in such scenario, it does something like: > > > > * mmap() memory region > > * fill in the pages that were collected during the pre-dump > > * do some other stuff > > * register memory region with userfaultfd > > * populate the missing memory on demand > > > > khugepaged collapses the pages in the partially populated regions before we > > have a chance to register these regions with userfaultfd, which would > > prevent the collapse. > > > > We could have used MADV_NOHUGEPAGE right after the mmap() call, and then > > there would be no race because there would be nothing for khugepaged to > > collapse at that point. But the problem is that we have no way to reset > > *HUGEPAGE flags after the memory restore is complete. > > Hmm, I wouldn't be that sure if this is indeed race-free. Check that > this scenario is indeed impossible? > > - you do the mmap > - khugepaged will choose the process' mm to scan > - khugepaged will get to the vma in question, it doesn't have > MADV_NOHUGEPAGE yet > - you set MADV_NOHUGEPAGE on the vma > - you start populating the vma > - khugepaged sees the vma is non-empty, collapses > > unless I'm wrong, the racers will have mmap_sem for reading only when > setting/checking the MADV_NOHUGEPAGE? Might be actually considered a bug. madvise(MADV_*HUGEPAGE) takes mmap_sem for writing, so it is safe. > However, can't you use prctl(PR_SET_THP_DISABLE) instead? "If arg2 has a > nonzero value, the flag is set, otherwise it is cleared." says the > manpage. Do it before the mmap and you avoid the race as well? I've missed that one, thanks Vlastimil! -- 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