Received: by 10.192.165.148 with SMTP id m20csp287219imm; Tue, 1 May 2018 23:38:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZppPotvWr6ubA8Wl0mYTnDsmi1uM+Ux6s6J2KvgldQtYlaKtAs3TTPYHXwhdOj64yBGvmc+ X-Received: by 2002:a17:902:8305:: with SMTP id bd5-v6mr18834040plb.13.1525243112462; Tue, 01 May 2018 23:38:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525243112; cv=none; d=google.com; s=arc-20160816; b=lKea9RrPpFVr4p5RCiGrDPDFT2WjlQlhqc8yMxsVQsyMYnVMNzqExpssxcSw/aZNL+ B9QS18+uVZgEE9fQwxUcVkE/KM/cAITpv3DZmqsmFVOV0m6m08PhdRvWUX4hpLHtWcLT QXrzeXBQdWM7ZQxYB0E81s414UXBsJ80v/V73wciBZCM+CVr/uKq6za/7Tm+yzQwbWGW T0jM0P2au8p+KI4chtAIcD90rcxiEyz6ymqVQUuhiIH67Og4RY87AtRsttpVZMbIQ60N zcvO9XE34KkJpoKCnvPNzEyRiMoboYr9gTHqeEu7UxWEpq2vj/s4GCd5+HUVZxwfzyBF iVUQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date:from :references:cc:to:subject:arc-authentication-results; bh=Xrx82zkVp7uG3a3EjKebzIGsyH0jmNC8tlQrJd9TdF0=; b=XDMihQWq/h8QaKATFsw7PcQwT54PDhLUY0Rftfm+DrJ1qjrNlLvtCGp4/OqidkwbTe 3ZF4z5zwx3F17zblNWCcInUakGVFs2GC52FG3UK/VwxMZxofqKomFUUeItkb17+YKNiU +xMLT2SR+V4fdfsOZimGSy+oWv5airvpsn83XyG7nj+WIAwM88vG8p5jBUmouDTJTTcM kwWMaeFT/YHQbmqkywEw9FuHPdp2VDLMR3HfjrETYZAXapOoXFesaQXzrOoXD2HDKB6j vdsrTk7Ya2BlM79+j/GUNky8FXc6uVRylQpSw/jMvXmbHy0/Kk+2qs38t8PO/YnABpZ9 PDIA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m37-v6si11023722pla.346.2018.05.01.23.38.18; Tue, 01 May 2018 23:38:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751075AbeEBGh5 (ORCPT + 99 others); Wed, 2 May 2018 02:37:57 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:51210 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750836AbeEBGhz (ORCPT ); Wed, 2 May 2018 02:37:55 -0400 Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w426Y9E6113485 for ; Wed, 2 May 2018 02:37:54 -0400 Received: from e06smtp14.uk.ibm.com (e06smtp14.uk.ibm.com [195.75.94.110]) by mx0b-001b2d01.pphosted.com with ESMTP id 2hq30nh0he-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 02 May 2018 02:37:54 -0400 Received: from localhost by e06smtp14.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 2 May 2018 07:37:52 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp14.uk.ibm.com (192.168.101.144) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 2 May 2018 07:37:43 +0100 Received: from d06av24.portsmouth.uk.ibm.com (d06av24.portsmouth.uk.ibm.com [9.149.105.60]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w426bgsN3277208; Wed, 2 May 2018 06:37:42 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 22F4C4204B; Wed, 2 May 2018 07:28:55 +0100 (BST) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DD2B142049; Wed, 2 May 2018 07:28:52 +0100 (BST) Received: from [9.145.16.142] (unknown [9.145.16.142]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 2 May 2018 07:28:52 +0100 (BST) Subject: Re: [PATCH v10 17/25] mm: protect mm_rb tree with a rwlock To: Punit Agrawal Cc: akpm@linux-foundation.org, mhocko@kernel.org, peterz@infradead.org, kirill@shutemov.name, ak@linux.intel.com, dave@stgolabs.net, jack@suse.cz, Matthew Wilcox , benh@kernel.crashing.org, mpe@ellerman.id.au, paulus@samba.org, Thomas Gleixner , Ingo Molnar , hpa@zytor.com, Will Deacon , Sergey Senozhatsky , Andrea Arcangeli , Alexei Starovoitov , kemi.wang@intel.com, sergey.senozhatsky.work@gmail.com, Daniel Jordan , David Rientjes , Jerome Glisse , Ganesh Mahendran , linux-kernel@vger.kernel.org, linux-mm@kvack.org, haren@linux.vnet.ibm.com, khandual@linux.vnet.ibm.com, npiggin@gmail.com, bsingharora@gmail.com, paulmck@linux.vnet.ibm.com, Tim Chen , linuxppc-dev@lists.ozlabs.org, x86@kernel.org References: <1523975611-15978-1-git-send-email-ldufour@linux.vnet.ibm.com> <1523975611-15978-18-git-send-email-ldufour@linux.vnet.ibm.com> From: Laurent Dufour Date: Wed, 2 May 2018 08:37:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18050206-0044-0000-0000-0000054E0147 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18050206-0045-0000-0000-0000288F1F94 Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-05-02_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1805020065 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Punit, Thanks for reviewing this series. On 30/04/2018 20:47, Punit Agrawal wrote: > Hi Laurent, > > One nitpick below. > > On Tue, Apr 17, 2018 at 3:33 PM, Laurent Dufour > wrote: >> This change is inspired by the Peter's proposal patch [1] which was >> protecting the VMA using SRCU. Unfortunately, SRCU is not scaling well in >> that particular case, and it is introducing major performance degradation >> due to excessive scheduling operations. >> >> To allow access to the mm_rb tree without grabbing the mmap_sem, this patch >> is protecting it access using a rwlock. As the mm_rb tree is a O(log n) >> search it is safe to protect it using such a lock. The VMA cache is not >> protected by the new rwlock and it should not be used without holding the >> mmap_sem. >> >> To allow the picked VMA structure to be used once the rwlock is released, a >> use count is added to the VMA structure. When the VMA is allocated it is >> set to 1. Each time the VMA is picked with the rwlock held its use count >> is incremented. Each time the VMA is released it is decremented. When the >> use count hits zero, this means that the VMA is no more used and should be >> freed. >> >> This patch is preparing for 2 kind of VMA access : >> - as usual, under the control of the mmap_sem, >> - without holding the mmap_sem for the speculative page fault handler. >> >> Access done under the control the mmap_sem doesn't require to grab the >> rwlock to protect read access to the mm_rb tree, but access in write must >> be done under the protection of the rwlock too. This affects inserting and >> removing of elements in the RB tree. >> >> The patch is introducing 2 new functions: >> - vma_get() to find a VMA based on an address by holding the new rwlock. >> - vma_put() to release the VMA when its no more used. >> These services are designed to be used when access are made to the RB tree >> without holding the mmap_sem. >> >> When a VMA is removed from the RB tree, its vma->vm_rb field is cleared and >> we rely on the WMB done when releasing the rwlock to serialize the write >> with the RMB done in a later patch to check for the VMA's validity. >> >> When free_vma is called, the file associated with the VMA is closed >> immediately, but the policy and the file structure remained in used until >> the VMA's use count reach 0, which may happens later when exiting an >> in progress speculative page fault. >> >> [1] https://patchwork.kernel.org/patch/5108281/ >> >> Cc: Peter Zijlstra (Intel) >> Cc: Matthew Wilcox >> Signed-off-by: Laurent Dufour >> --- >> include/linux/mm.h | 1 + >> include/linux/mm_types.h | 4 ++ >> kernel/fork.c | 3 ++ >> mm/init-mm.c | 3 ++ >> mm/internal.h | 6 +++ >> mm/mmap.c | 115 +++++++++++++++++++++++++++++++++++------------ >> 6 files changed, 104 insertions(+), 28 deletions(-) >> > > [...] > >> diff --git a/mm/mmap.c b/mm/mmap.c >> index 5601f1ef8bb9..a82950960f2e 100644 >> --- a/mm/mmap.c >> +++ b/mm/mmap.c >> @@ -160,6 +160,27 @@ void unlink_file_vma(struct vm_area_struct *vma) >> } >> } >> >> +static void __free_vma(struct vm_area_struct *vma) >> +{ >> + if (vma->vm_file) >> + fput(vma->vm_file); >> + mpol_put(vma_policy(vma)); >> + kmem_cache_free(vm_area_cachep, vma); >> +} >> + >> +#ifdef CONFIG_SPECULATIVE_PAGE_FAULT >> +void put_vma(struct vm_area_struct *vma) >> +{ >> + if (atomic_dec_and_test(&vma->vm_ref_count)) >> + __free_vma(vma); >> +} >> +#else >> +static inline void put_vma(struct vm_area_struct *vma) >> +{ >> + return __free_vma(vma); > > Please drop the "return". Sure ! Thanks. > > Thanks, > Punit > > [...] >