From: Wei Yang <richard.weiyang@linux.alibaba.com>
To: 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,
richard.weiyang@linux.alibaba.com, peterx@redhat.com,
aneesh.kumar@linux.ibm.com, willy@infradead.org,
thellstrom@vmware.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, digetx@gmail.com
Subject: [Patch v5 0/3] mm/mremap: cleanup move_page_tables() a little
Date: Fri, 10 Jul 2020 17:28:32 +0800 [thread overview]
Message-ID: <20200710092835.56368-1-richard.weiyang@linux.alibaba.com> (raw)
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.
v5:
* remove the last patch which breaks on ARM
v4:
* remove a redundant parentheses pointed by Kirill
v3:
* merge patch 1 with 2 as suggested by Kirill
* add patch 4 to simplify the logic to calculate next and extent
v2:
* remove 3rd patch which doesn't work on ARM platform. Thanks report and
test from Dmitry Osipenko
Wei Yang (3):
mm/mremap: it is sure to have enough space when extent meets
requirement
mm/mremap: calculate extent in one place
mm/mremap: start addresses are properly aligned
include/linux/huge_mm.h | 2 +-
mm/huge_memory.c | 8 +-------
mm/mremap.c | 17 ++++++-----------
3 files changed, 8 insertions(+), 19 deletions(-)
--
2.20.1 (Apple Git-117)
next reply other threads:[~2020-07-10 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 9:28 Wei Yang [this message]
2020-07-10 9:28 ` [Patch v5 1/3] mm/mremap: it is sure to have enough space when extent meets requirement Wei Yang
2020-07-10 9:28 ` [Patch v5 2/3] mm/mremap: calculate extent in one place Wei Yang
2020-07-10 9:28 ` [Patch v5 3/3] mm/mremap: start addresses are properly aligned Wei Yang
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=20200710092835.56368-1-richard.weiyang@linux.alibaba.com \
--to=richard.weiyang@linux.alibaba.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.