From: Chintan Pandya <cpandya@codeaurora.org>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
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
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: vmalloc: Remove double execution of vunmap_page_range
Date: Fri, 13 Apr 2018 15:47:02 +0530 [thread overview]
Message-ID: <8da9f826-2a3d-e618-e512-4fc8d45c16f2@codeaurora.org> (raw)
In-Reply-To: <a623e12b-bb5e-58fa-c026-de9ea53c5bd9@linux.vnet.ibm.com>
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
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().
Chintan
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center,
Inc. is a member of the Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2018-04-13 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 9:16 Chintan Pandya
2018-04-13 9:59 ` Anshuman Khandual
2018-04-13 10:17 ` Chintan Pandya [this message]
2018-04-13 10:40 ` Anshuman Khandual
2018-04-13 10:45 ` Chintan Pandya
2018-04-13 11:09 ` Michal Hocko
2018-04-13 11:27 ` Chintan Pandya
2018-04-13 11:41 ` Michal Hocko
2018-04-13 12:12 ` Chintan Pandya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8da9f826-2a3d-e618-e512-4fc8d45c16f2@codeaurora.org \
--to=cpandya@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=byungchul.park@lge.com \
--cc=catalin.marinas@arm.com \
--cc=f.fainelli@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox