Received: by 10.192.165.156 with SMTP id m28csp551533imm; Fri, 13 Apr 2018 03:58:01 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+QJnsBPiGzgy1mov7t+zr7CAzBLC/0oeIAPdQ77Xg7VEQG9fn3eEeqke7x51BlTvC5jibd X-Received: by 10.99.98.66 with SMTP id w63mr2786419pgb.377.1523617081675; Fri, 13 Apr 2018 03:58:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523617081; cv=none; d=google.com; s=arc-20160816; b=ot5G9vm6n1x8rNOiVRNrmkeXINwMyh+FoUycCMvE+gFQus1DPj4UgKwWtgOpYEvz0+ RVZZiIZavyOY/OQZLwQUNFdOgMEPPsgzgWeaXxXEFV8uPqPHcpU7oWC9SQfgw41cb69W cxZxhgHG9WqFgC3bghqoxcKVxlTGa4azBHrx8/SaRYzoJHyf0nv44uxRWwoslhRPpecP n3DwxCTqe7wEwwEfB05dG3zR3XXMOumo+FNk5YFadyDqZi9BUaULOYX61Rv2vG1G2oyl xwEnve+kQqPt+/l2inLvB6LRBMSuMNHZFQWMbxPa42tCtVkn+8wZECEXeB/oXHg1QxxI smOQ== 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 :in-reply-to:mime-version:user-agent:date:from:cc:references:to :subject:arc-authentication-results; bh=56/UV4497i7iQJ0PasKsdp5IuepuD2WyBuiWoXGox3o=; b=x5EPM/6SWfJ5H8voAb9AuTYwoDKGxuwBxNJTQ/yUXG6alGE3UsHoqiaStfnCF7F+SZ qAJ2OqaYJyidmyfJ81yO/KAz2hf2hnARck/409EzRw8NftVY6BV+nRYibnMwbDVOcuyb 4t0/Z6LtllJRsdMn9P+ktCPPjmGWIqhfMWalAHo5xzQOjiKSfjwZbze9PfEiHaFfKzJ5 JFp8yL/YbJNLX5TcvB1fbg1wqdf9VAwtqO3c+vpaCDYvz47K6pCWek4znv9PYqhbfUUn MPr/1hOHg0lXimhWyKYX2f1SODnhfD6rSBfMynAcYntKb6cqW8CGzlrBDPU3HN6EZfBH WXZQ== 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 a21si4260533pfn.281.2018.04.13.03.57.48; Fri, 13 Apr 2018 03:58:01 -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 S1754289AbeDMKkm (ORCPT + 99 others); Fri, 13 Apr 2018 06:40:42 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:46352 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753634AbeDMKkk (ORCPT ); Fri, 13 Apr 2018 06:40:40 -0400 Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w3DAddI1036076 for ; Fri, 13 Apr 2018 06:40:40 -0400 Received: from e06smtp15.uk.ibm.com (e06smtp15.uk.ibm.com [195.75.94.111]) by mx0b-001b2d01.pphosted.com with ESMTP id 2haqm417j2-1 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NOT) for ; Fri, 13 Apr 2018 06:40:39 -0400 Received: from localhost by e06smtp15.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 13 Apr 2018 11:40:36 +0100 Received: from b06cxnps4074.portsmouth.uk.ibm.com (9.149.109.196) by e06smtp15.uk.ibm.com (192.168.101.145) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 13 Apr 2018 11:40:33 +0100 Received: from d06av22.portsmouth.uk.ibm.com (d06av22.portsmouth.uk.ibm.com [9.149.105.58]) by b06cxnps4074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id w3DAeXnt46858400; Fri, 13 Apr 2018 10:40:33 GMT Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id C32E04C062; Fri, 13 Apr 2018 11:33:09 +0100 (BST) Received: from d06av22.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 04F994C04E; Fri, 13 Apr 2018 11:33:07 +0100 (BST) Received: from [9.202.15.240] (unknown [9.202.15.240]) by d06av22.portsmouth.uk.ibm.com (Postfix) with ESMTP; Fri, 13 Apr 2018 11:33:06 +0100 (BST) Subject: Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range To: Chintan Pandya , Anshuman Khandual , vbabka@suse.cz, labbott@redhat.com, catalin.marinas@arm.com, hannes@cmpxchg.org, f.fainelli@gmail.com, xieyisheng1@huawei.com, ard.biesheuvel@linaro.org, richard.weiyang@gmail.com, byungchul.park@lge.com References: <1523611019-17679-1-git-send-email-cpandya@codeaurora.org> <8da9f826-2a3d-e618-e512-4fc8d45c16f2@codeaurora.org> Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org From: Anshuman Khandual Date: Fri, 13 Apr 2018 16:10:29 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <8da9f826-2a3d-e618-e512-4fc8d45c16f2@codeaurora.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 18041310-0020-0000-0000-000004117EDE X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 18041310-0021-0000-0000-000042A5B0FF Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-04-13_05:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=2 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000 definitions=main-1804130099 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/13/2018 03:47 PM, Chintan Pandya wrote: > > > On 4/13/2018 3:29 PM, Anshuman Khandual wrote: >> On 04/13/2018 02:46 PM, Chintan Pandya wrote: >>> Unmap legs do call vunmap_page_range() irrespective of >>> debug_pagealloc_enabled() is enabled or not. So, remove >>> redundant check and optional vunmap_page_range() routines. >> >> vunmap_page_range() tears down the page table entries and does >> not really flush related TLB entries normally unless page alloc >> debug is enabled where it wants to make sure no stale mapping is >> still around for debug purpose. Deferring TLB flush improves >> performance. This patch will force TLB flush during each page >> table tear down and hence not desirable. >> > Deferred TLB invalidation will surely improve performance. But force > flush can help in detecting invalid access right then and there. I Deferred TLB invalidation was a choice made some time ago with the commit db64fe02258f1507e ("mm: rewrite vmap layer") as these vmalloc mappings wont be used other than inside the kernel and TLB gets flushed when they are reused. This way it can still avail the benefit of deferred TLB flushing without exposing itself to invalid accesses. > chose later. May be I should have clean up the vmap tear down code > as well where it actually does the TLB invalidation. > > Or make TLB invalidation in free_unmap_vmap_area() be dependent upon > debug_pagealloc_enabled(). Immediate TLB invalidation needs to be dependent on debug_pagealloc_ enabled() and should be done only for debug purpose. Contrary to that is not desirable.