From: "Li Xinhai" <lixinhai.lxh@gmail.com>
To: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Mike Kravetz" <mike.kravetz@oracle.com>
Cc: n-horiguchi <n-horiguchi@ah.jp.nec.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
akpm <akpm@linux-foundation.org>, mhocko <mhocko@suse.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] mm/mempolicy: support MPOL_MF_STRICT for huge page mapping
Date: Wed, 12 Feb 2020 13:25:04 +0800 [thread overview]
Message-ID: <2020021213250278382352@gmail.com> (raw)
In-Reply-To: 20200212032139.GA31425@hori.linux.bs1.fc.nec.co.jp
On 2020-02-12 at 11:21 HORIGUCHI NAOYA(堀口 直也) wrote:
>On Mon, Feb 10, 2020 at 09:19:48AM -0800, Mike Kravetz wrote:
>> On 1/30/20 5:33 PM, Li Xinhai wrote:
>...
>> >
>> > 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>
>>
>> Hello Naoya,
>>
>> Do you have any thoughts on this? In previous discussions you suggested this
>> approach of removing the special casing for hugetlb pages. The code looks
>> good to me and patch is fine with commmit message modification. Just wanted
>> to get your opinion.
>
>Hi Mike, Xinhai,
>
>The suggested change looks good to me, too.
>
>Thanks,
>Naoya Horiguchi
Naoya, thanks for inspecting the change!
next prev parent reply other threads:[~2020-02-12 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 1:33 [PATCH] mm/mempolicy: support MPOL_MF_STRICT for huge page mapping Li Xinhai
2020-02-01 3:28 ` Mike Kravetz
2020-02-01 13:56 ` Li Xinhai
2020-02-10 17:19 ` Mike Kravetz
2020-02-12 3:21 ` HORIGUCHI NAOYA(堀口 直也)
2020-02-12 5:25 ` Li Xinhai [this message]
2020-02-12 23:50 ` Mike Kravetz
2020-02-13 1:50 ` Li Xinhai
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=2020021213250278382352@gmail.com \
--to=lixinhai.lxh@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=naoya.horiguchi@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).