From: Wei Yang <richardw.yang@linux.intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richardw.yang@linux.intel.com>,
dan.j.williams@intel.com, aneesh.kumar@linux.ibm.com,
kirill@shutemov.name, yang.shi@linux.alibaba.com,
thellstrom@vmware.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 0/5] mm/mremap.c: cleanup move_page_tables() a little
Date: Sun, 19 Jan 2020 10:11:07 +0800 [thread overview]
Message-ID: <20200119021107.GA9745@richard> (raw)
In-Reply-To: <20200118160702.9e5cc9f44ef855c070036331@linux-foundation.org>
On Sat, Jan 18, 2020 at 04:07:02PM -0800, Andrew Morton wrote:
>On Sat, 18 Jan 2020 07:22:49 +0800 Wei Yang <richardw.yang@linux.intel.com> wrote:
>
>> move_page_tables() tries to move page table by PMD or PTE.
>>
>> The root reason is if it tries to move PMD, both old and new range should
>> be PMD aligned. But current code calculate old range and new range
>> separately. This leads to some redundant check and calculation.
>>
>> This cleanup tries to consolidate the range check in one place to reduce
>> some extra range handling.
>
>Thanks, I grabbed these, aimed at 5.7-rc1.
Thanks :)
--
Wei Yang
Help you, Help me
prev parent reply other threads:[~2020-01-19 2:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 23:22 [PATCH 0/5] mm/mremap.c: cleanup move_page_tables() a little Wei Yang
2020-01-17 23:22 ` [PATCH 1/5] mm/mremap: format the check in move_normal_pmd() same as move_huge_pmd() Wei Yang
2020-01-17 23:22 ` [PATCH 2/5] mm/mremap: it is sure to have enough space when extent meets requirement Wei Yang
2020-01-17 23:22 ` [PATCH 3/5] mm/mremap: use pmd_addr_end to calculate next in move_page_tables() Wei Yang
2020-01-26 14:47 ` Dmitry Osipenko
2020-01-27 2:59 ` Andrew Morton
2020-01-29 17:18 ` Dmitry Osipenko
2020-01-29 23:59 ` Andrew Morton
2020-01-30 0:28 ` Stephen Rothwell
2020-01-28 0:43 ` Wei Yang
2020-01-28 15:59 ` Dmitry Osipenko
2020-01-28 23:29 ` Wei Yang
2020-01-28 23:35 ` Dmitry Osipenko
2020-01-29 0:28 ` Wei Yang
2020-01-29 18:56 ` Dmitry Osipenko
2020-01-29 9:47 ` Russell King - ARM Linux admin
2020-01-29 14:21 ` Dmitry Osipenko
2020-01-29 21:57 ` Wei Yang
2020-01-29 23:24 ` Russell King - ARM Linux admin
2020-01-30 1:30 ` Wei Yang
2020-01-30 14:15 ` Russell King - ARM Linux admin
2020-01-30 21:57 ` Wei Yang
2020-01-17 23:22 ` [PATCH 4/5] mm/mremap: calculate extent in one place Wei Yang
2020-01-17 23:22 ` [PATCH 5/5] mm/mremap: start addresses are properly aligned Wei Yang
2020-01-19 0:07 ` [PATCH 0/5] mm/mremap.c: cleanup move_page_tables() a little Andrew Morton
2020-01-19 2:11 ` Wei Yang [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=20200119021107.GA9745@richard \
--to=richardw.yang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=thellstrom@vmware.com \
--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;
as well as URLs for NNTP newsgroup(s).