From: Wei Yang <richard.weiyang@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
vbabka@suse.cz, mgorman@techsingularity.net, mhocko@suse.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_alloc: return 0 in case this node has no page within the zone
Date: Tue, 7 Feb 2017 23:07:08 +0800 [thread overview]
Message-ID: <20170207150708.GA31837@WeideMBP.lan> (raw)
In-Reply-To: <20170206152932.19e7947df487b96b8912e524@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Mon, Feb 06, 2017 at 03:29:32PM -0800, Andrew Morton wrote:
>On Mon, 6 Feb 2017 23:43:14 +0800 Wei Yang <richard.weiyang@gmail.com> wrote:
>
>> The whole memory space is divided into several zones and nodes may have no
>> page in some zones. In this case, the __absent_pages_in_range() would
>> return 0, since the range it is searching for is an empty range.
>>
>> Also this happens more often to those nodes with higher memory range when
>> there are more nodes, which is a trend for future architectures.
>>
>> This patch checks the zone range after clamp and adjustment, return 0 if
>> the range is an empty range.
>
>What are the user-visible runtime effects of this change?
Hmm, for users they may not "see" the effect, while it will save some time in
case there is no overlap between the zone and node.
--
Wei Yang
Help you, Help me
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-07 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 15:43 [PATCH] mm/page_alloc: return 0 in case this node has no page within the zone Wei Yang
2017-02-06 23:29 ` Andrew Morton
2017-02-07 15:07 ` Wei Yang [this message]
2017-02-07 9:45 ` Michal Hocko
2017-02-07 15:32 ` Wei Yang
2017-02-07 15:41 ` Michal Hocko
2017-02-08 14:05 ` Wei Yang
2017-02-08 14:39 ` Michal Hocko
2017-02-09 13:59 ` Wei Yang
2017-02-22 8:49 ` Michal Hocko
2017-02-22 10:51 ` Wei Yang
2017-02-22 11:45 ` Michal Hocko
2017-02-22 14:18 ` 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=20170207150708.GA31837@WeideMBP.lan \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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).