From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Wei Yang <richard.weiyang@linux.alibaba.com>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
vbabka@suse.cz, yang.shi@linux.alibaba.com,
thomas_os@shipmail.org, anshuman.khandual@arm.com,
sean.j.christopherson@intel.com, peterx@redhat.com,
aneesh.kumar@linux.ibm.com, willy@infradead.org,
thellstrom@vmware.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, digetx@gmail.com
Subject: Re: [Patch v3 4/4] mm/mremap: use pmd_addr_end to simplify the calculate of extent
Date: Wed, 8 Jul 2020 11:27:00 +0300 [thread overview]
Message-ID: <20200708082700.ev7m5re42tupixqu@box> (raw)
In-Reply-To: <20200708012453.36588-5-richard.weiyang@linux.alibaba.com>
On Wed, Jul 08, 2020 at 09:24:53AM +0800, Wei Yang wrote:
> The purpose of this code is to calculate the smaller extent in old and
> new range. Let's leverage pmd_addr_end() to do the calculation.
>
> Hope this would make the code easier to read.
>
> Signed-off-by: Wei Yang <richard.weiyang@linux.alibaba.com>
> ---
> mm/mremap.c | 16 +++++++---------
> 1 file changed, 7 insertions(+), 9 deletions(-)
>
> diff --git a/mm/mremap.c b/mm/mremap.c
> index f5f17d050617..76e7fdf567c3 100644
> --- a/mm/mremap.c
> +++ b/mm/mremap.c
> @@ -237,11 +237,12 @@ unsigned long move_page_tables(struct vm_area_struct *vma,
> unsigned long new_addr, unsigned long len,
> bool need_rmap_locks)
> {
> - unsigned long extent, next, old_end;
> + unsigned long extent, old_next, new_next, old_end, new_end;
> struct mmu_notifier_range range;
> pmd_t *old_pmd, *new_pmd;
>
> old_end = old_addr + len;
> + new_end = new_addr + len;
> flush_cache_range(vma, old_addr, old_end);
>
> mmu_notifier_range_init(&range, MMU_NOTIFY_UNMAP, 0, vma, vma->vm_mm,
> @@ -250,14 +251,11 @@ unsigned long move_page_tables(struct vm_area_struct *vma,
>
> for (; old_addr < old_end; old_addr += extent, new_addr += extent) {
> cond_resched();
> - next = (old_addr + PMD_SIZE) & PMD_MASK;
> - /* even if next overflowed, extent below will be ok */
> - extent = next - old_addr;
> - if (extent > old_end - old_addr)
> - extent = old_end - old_addr;
> - next = (new_addr + PMD_SIZE) & PMD_MASK;
> - if (extent > next - new_addr)
> - extent = next - new_addr;
> +
> + old_next = pmd_addr_end(old_addr, old_end);
> + new_next = pmd_addr_end(new_addr, new_end);
> + extent = min((old_next - old_addr), (new_next - new_addr));
Nit: redundant parentheses.
--
Kirill A. Shutemov
prev parent reply other threads:[~2020-07-08 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 1:24 [Patch v3 0/4] mm/mremap: cleanup move_page_tables() a little Wei Yang
2020-07-08 1:24 ` [Patch v3 1/4] mm/mremap: it is sure to have enough space when extent meets requirement Wei Yang
2020-07-08 1:24 ` [Patch v3 2/4] mm/mremap: calculate extent in one place Wei Yang
2020-07-08 1:24 ` [Patch v3 3/4] mm/mremap: start addresses are properly aligned Wei Yang
2020-07-08 1:24 ` [Patch v3 4/4] mm/mremap: use pmd_addr_end to simplify the calculate of extent Wei Yang
2020-07-08 8:27 ` Kirill A. Shutemov [this message]
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=20200708082700.ev7m5re42tupixqu@box \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=anshuman.khandual@arm.com \
--cc=digetx@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=sean.j.christopherson@intel.com \
--cc=thellstrom@vmware.com \
--cc=thomas_os@shipmail.org \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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