linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: <akpm@linux-foundation.org>, <tglx@linutronix.de>,
	<mingo@redhat.com>, <peterz@infradead.org>,
	<dvhart@infradead.org>, <dave@stgolabs.net>,
	<andrealmeid@igalia.com>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/mm_init.c: remove obsolete macro HASH_SMALL
Date: Sat, 17 Jun 2023 16:39:44 +0800	[thread overview]
Message-ID: <6d149902-a944-7961-89c1-f07047953c7f@huawei.com> (raw)
In-Reply-To: <20230617075644.GV52412@kernel.org>

On 2023/6/17 15:56, Mike Rapoport wrote:
> On Sat, Jun 17, 2023 at 03:09:55PM +0800, Miaohe Lin wrote:
>> HASH_SMALL only works when parameter numentries is 0. But the sole caller
>> futex_init() never calls alloc_large_system_hash() with numentries set to
>> 0. 
> 

Thanks for your quick review.

> Doesn't it? 
> What happens when CONFIG_BASE_SMALL is set?

When CONFIG_BASE_SMALL is set, futex_hashsize is set to 16 and alloc_large_system_hash() is called with
numentries == 16 && flags == HASH_SMALL. But in the alloc_large_system_hash(), we have the below logic:

alloc_large_system_hash()
{
  if (!numentries) { /* numentries == 16 here, so this code block is skipped. */
    ...
    if (unlikely(flags & HASH_SMALL)) { /* So as here. */
      ...
  }
  ...
}

So HASH_SMALL is just unused. Or am I miss something?

Thanks.

> 
>> So HASH_SMALL is obsolete and remove it.
> 
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>>  include/linux/memblock.h |  2 --
>>  kernel/futex/core.c      |  3 +--
>>  mm/mm_init.c             | 10 +---------
>>  3 files changed, 2 insertions(+), 13 deletions(-)
>>
>> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
>> index f71ff9f0ec81..346d80809517 100644
>> --- a/include/linux/memblock.h
>> +++ b/include/linux/memblock.h
>> @@ -581,8 +581,6 @@ extern void *alloc_large_system_hash(const char *tablename,
>>  				     unsigned long high_limit);
>>  
>>  #define HASH_EARLY	0x00000001	/* Allocating during early boot? */
>> -#define HASH_SMALL	0x00000002	/* sub-page allocation allowed, min
>> -					 * shift passed via *_hash_shift */
>>  #define HASH_ZERO	0x00000004	/* Zero allocated hash table */
>>  
>>  /* Only NUMA needs hash distribution. 64bit NUMA architectures have
>> diff --git a/kernel/futex/core.c b/kernel/futex/core.c
>> index 514e4582b863..f10587d1d481 100644
>> --- a/kernel/futex/core.c
>> +++ b/kernel/futex/core.c
>> @@ -1132,8 +1132,7 @@ static int __init futex_init(void)
>>  #endif
>>  
>>  	futex_queues = alloc_large_system_hash("futex", sizeof(*futex_queues),
>> -					       futex_hashsize, 0,
>> -					       futex_hashsize < 256 ? HASH_SMALL : 0,
>> +					       futex_hashsize, 0, 0,
>>  					       &futex_shift, NULL,
>>  					       futex_hashsize, futex_hashsize);
>>  	futex_hashsize = 1UL << futex_shift;
>> diff --git a/mm/mm_init.c b/mm/mm_init.c
>> index d393631599a7..fab3c4649d5b 100644
>> --- a/mm/mm_init.c
>> +++ b/mm/mm_init.c
>> @@ -2492,15 +2492,7 @@ void *__init alloc_large_system_hash(const char *tablename,
>>  		else
>>  			numentries <<= (PAGE_SHIFT - scale);
>>  
>> -		/* Make sure we've got at least a 0-order allocation.. */
>> -		if (unlikely(flags & HASH_SMALL)) {
>> -			/* Makes no sense without HASH_EARLY */
>> -			WARN_ON(!(flags & HASH_EARLY));
>> -			if (!(numentries >> *_hash_shift)) {
>> -				numentries = 1UL << *_hash_shift;
>> -				BUG_ON(!numentries);
>> -			}
>> -		} else if (unlikely((numentries * bucketsize) < PAGE_SIZE))
>> +		if (unlikely((numentries * bucketsize) < PAGE_SIZE))
>>  			numentries = PAGE_SIZE / bucketsize;
>>  	}
>>  	numentries = roundup_pow_of_two(numentries);
>> -- 
>> 2.27.0
>>
> 



  reply	other threads:[~2023-06-17  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  7:09 Miaohe Lin
2023-06-17  7:56 ` Mike Rapoport
2023-06-17  8:39   ` Miaohe Lin [this message]
2023-06-17 10:51     ` Mike Rapoport
2023-06-19  1:34       ` Miaohe Lin

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=6d149902-a944-7961-89c1-f07047953c7f@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrealmeid@igalia.com \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rppt@kernel.org \
    --cc=tglx@linutronix.de \
    /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