From: David Rientjes <rientjes@google.com>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, mhocko@suse.com,
mingo@kernel.org, n-horiguchi@ah.jp.nec.com, salls@cs.ucsb.edu,
ak@linux.intel.com, cl@linux.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
tanxiaojun@huawei.com
Subject: Re: [PATCH v3 1/3] mm/mempolicy: remove redundant check in get_nodes
Date: Mon, 20 Nov 2017 14:24:21 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1711201424100.42955@chino.kir.corp.google.com> (raw)
In-Reply-To: <1510882624-44342-2-git-send-email-xieyisheng1@huawei.com>
On Fri, 17 Nov 2017, Yisheng Xie wrote:
> We have already checked whether maxnode is a page worth of bits, by:
> maxnode > PAGE_SIZE*BITS_PER_BYTE
>
> So no need to check it once more.
>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
Acked-by: David Rientjes <rientjes@google.com>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-20 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 1:37 [PATCH v3 0/3] some fixes and clean up for mempolicy Yisheng Xie
2017-11-17 1:37 ` [PATCH v3 1/3] mm/mempolicy: remove redundant check in get_nodes Yisheng Xie
2017-11-20 22:24 ` David Rientjes [this message]
2017-11-17 1:37 ` [PATCH v3 2/3] mm/mempolicy: fix the check of nodemask from user Yisheng Xie
2017-11-27 17:05 ` Vlastimil Babka
2017-11-17 1:37 ` [PATCH v3 3/3] mm/mempolicy: add nodes_empty check in SYSC_migrate_pages Yisheng Xie
2017-11-27 17:25 ` Vlastimil Babka
2017-11-28 2:03 ` Yisheng Xie
2017-11-28 8:04 ` Yisheng Xie
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=alpine.DEB.2.10.1711201424100.42955@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=salls@cs.ucsb.edu \
--cc=tanxiaojun@huawei.com \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.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