From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: Li Xinhai <lixinhai.lxh@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH v2] mm/mempolicy: support MPOL_MF_STRICT for huge page mapping
Date: Fri, 14 Feb 2020 03:36:32 +0000 [thread overview]
Message-ID: <20200214033632.GA20790@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <1581559627-6206-1-git-send-email-lixinhai.lxh@gmail.com>
On Thu, Feb 13, 2020 at 02:07:07AM +0000, Li Xinhai wrote:
> MPOL_MF_STRICT is used in mbind() for purposes:
> (1) MPOL_MF_STRICT is set alone without MPOL_MF_MOVE or MPOL_MF_MOVE_ALL,
> to check if there is misplaced page and return -EIO;
> (2) MPOL_MF_STRICT is set with MPOL_MF_MOVE or MPOL_MF_MOVE_ALL, to check
> if there is misplaced page which is failed to isolate, or page is
> success on isolate but failed to move, and return -EIO.
>
> For non hugepage mapping, (1) and (2) are implemented as expectation.
> For hugepage mapping, (1) is not implemented. And in (2), the part about
> failed to isolate and report -EIO is not implemented.
>
> This patch implements the missed parts for hugepage mapping. Benefits
> with it applied:
> - User space can apply same code logic to handle mbind() on hugepage and
> non hugepage mapping;
> - Reliably using MPOL_MF_STRICT alone to check whether there is misplaced
> page or not when bind policy on address range, especially for address
> range which contains both hugepage and non hugepage mapping.
>
> Analysis of potential impact to existing users:
> - If MPOL_MF_STRICT alone was previously used, hugetlb pages not following
> the memory policy would not cause an EIO error. After this change,
> hugetlb pages are treated like all other pages. If MPOL_MF_STRICT alone
> is used and hugetlb pages do not follow memory policy an EIO error will
> be returned.
> - For users who using MPOL_MF_STRICT with MPOL_MF_MOVE or
> MPOL_MF_MOVE_ALL, the semantic about some pages could not be moved will
> not be changed by this patch, because failed to isolate and failed to
> move have same effects to users, so their existing code will not be
> impacted.
>
> In mbind man page, the note about 'MPOL_MF_STRICT is ignored on huge page
> mappings' can be removed after this patch is applied.
>
> Signed-off-by: Li Xinhai <lixinhai.lxh@gmail.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> Cc: linux-man <linux-man@vger.kernel.org>
Thanks,
Reviewed-by: Naoya Horiguchi <naoya.horiguchi@nec.com>
prev parent reply other threads:[~2020-02-14 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 2:07 [PATCH v2] mm/mempolicy: support MPOL_MF_STRICT for huge page mapping Li Xinhai
2020-02-13 16:17 ` Mike Kravetz
2020-02-14 3:36 ` HORIGUCHI NAOYA(堀口 直也) [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=20200214033632.GA20790@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lixinhai.lxh@gmail.com \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.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).