linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Mike Rapoport <rppt@kernel.org>, Leesoo Ahn <lsahn@ooseel.net>
Cc: Leesoo Ahn <lsahn@wewakecorp.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/sparse: return right away if sparsemap_buf is null
Date: Mon, 29 Jul 2024 12:27:36 +0530	[thread overview]
Message-ID: <f71502d2-d216-4377-965f-21583dd7dc31@arm.com> (raw)
In-Reply-To: <ZqY81pf9dvl6mvg9@kernel.org>



On 7/28/24 18:13, Mike Rapoport wrote:
> On Fri, Jul 26, 2024 at 04:10:23PM +0900, Leesoo Ahn wrote:
>> sparse_buffer_fini(..) takes the following actions even though the value of
>> sparsemap_buf is NULL,
>> 1. calculate size of sparsemap buffer (which is meaningless).
>> 2. set sparsemap_buf variable to NULL (although it is already NULL).
>>
>> These steps are unnecessary if the variable, sparsemap_buf is NULL.
>>
>> Refactor the function to return right away if the variable is NULL.
>> Hence, it doesn't need to take further actions.
> 
> sparse_buffer_fini() is called a few times on init so saving a jump (if at
> all) does not worth the churn.

Agreed, this is not worth the churn given there could be just a single
call instance for sparse_buffer_fini(), either in normal or error path
in sparse_init_nid().

>  
>> Signed-off-by: Leesoo Ahn <lsahn@ooseel.net>
>> ---
>>  mm/sparse.c | 8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/sparse.c b/mm/sparse.c
>> index e4b830091d13..091e4bc2f72c 100644
>> --- a/mm/sparse.c
>> +++ b/mm/sparse.c
>> @@ -469,9 +469,13 @@ static void __init sparse_buffer_init(unsigned long size, int nid)
>>  
>>  static void __init sparse_buffer_fini(void)
>>  {
>> -	unsigned long size = sparsemap_buf_end - sparsemap_buf;
>> +	unsigned long size;
>>  
>> -	if (sparsemap_buf && size > 0)
>> +	if (!sparsemap_buf)
>> +		return;
>> +
>> +	size = sparsemap_buf_end - sparsemap_buf;
>> +	if (size > 0)
>>  		sparse_buffer_free(size);
>>  	sparsemap_buf = NULL;
>>  }
>> -- 
>> 2.34.1
>>
>>
> 


      reply	other threads:[~2024-07-29  6:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-26  7:10 Leesoo Ahn
2024-07-28 12:43 ` Mike Rapoport
2024-07-29  6:57   ` Anshuman Khandual [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=f71502d2-d216-4377-965f-21583dd7dc31@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsahn@ooseel.net \
    --cc=lsahn@wewakecorp.com \
    --cc=rppt@kernel.org \
    /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