linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, jgg@ziepe.ca,
	bhe@redhat.com
Subject: Re: [Patch v3] mm/page_alloc.c: use NODE_MASK_NONE define used_mask
Date: Mon, 30 Mar 2020 17:00:51 +0200	[thread overview]
Message-ID: <836fef2a-214b-63b1-4fa1-ade9fc642137@redhat.com> (raw)
In-Reply-To: <8d6a1cd3-75cf-78c3-b83b-c5208a209f65@nvidia.com>

On 29.03.20 06:00, John Hubbard wrote:
> On 3/28/20 7:42 PM, Wei Yang wrote:
>> For all 0 nodemask_t, we have already define macro NODE_MASK_NONE.
>> Leverage this to define an all clear nodemask.
> 
> It would be a little clearer if you used wording more like this:
> 
> Subject: [Patch v3] mm/page_alloc.c: use NODE_MASK_NONE in build_zonelists()
> 
> Slightly simplify the code by initializing user_mask with
> NODE_MASK_NONE, instead of later calling nodes_clear(). This saves
> a line of code.
> 
> 
>>
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>>
>> ---
>> v3: adjust the commit log a little
>> v2: use NODE_MASK_NONE as suggested by David Hildenbrand
>> ---
>>   mm/page_alloc.c | 3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
>> index ef790dfad6aa..dfcf2682ed40 100644
>> --- a/mm/page_alloc.c
>> +++ b/mm/page_alloc.c
>> @@ -5587,14 +5587,13 @@ static void build_zonelists(pg_data_t *pgdat)
>>   {
>>   	static int node_order[MAX_NUMNODES];
>>   	int node, load, nr_nodes = 0;
>> -	nodemask_t used_mask;
>> +	nodemask_t used_mask = NODE_MASK_NONE;
>>   	int local_node, prev_node;
>>   
>>   	/* NUMA-aware ordering of nodes */
>>   	local_node = pgdat->node_id;
>>   	load = nr_online_nodes;
>>   	prev_node = local_node;
>> -	nodes_clear(used_mask);
>>   
>>   	memset(node_order, 0, sizeof(node_order));
>>   	while ((node = find_next_best_node(local_node, &used_mask)) >= 0) {
>>
> 
> Honestly, I don't think it's really worth doing a patch for this, but
> there's nothing wrong with the diff, so:
> 
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>

With the changed subject/description

Reviewed-by: David Hildenbrand <david@redhat.com>


-- 
Thanks,

David / dhildenb



      parent reply	other threads:[~2020-03-30 15:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29  2:42 Wei Yang
2020-03-29  4:00 ` John Hubbard
2020-03-29  6:09   ` Wei Yang
2020-03-30 15:00   ` David Hildenbrand [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=836fef2a-214b-63b1-4fa1-ade9fc642137@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=richard.weiyang@gmail.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