linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/workingset.c: avoid unnecessary max_nodes estimation in count_shadow_nodes()
Date: Tue, 26 Jan 2021 17:24:57 +0100	[thread overview]
Message-ID: <8dea8eff-3100-4f57-5d61-e532803d256f@suse.cz> (raw)
In-Reply-To: <20210123073825.46709-1-linmiaohe@huawei.com>

On 1/23/21 8:38 AM, Miaohe Lin wrote:
> If list_lru_shrink_count is 0, we always return SHRINK_EMPTY regardless of
> the value of max_nodes. So we can return early if nodes == 0 to save some
> cpu cycles of approximating a reasonable limit for the nodes.
> 
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>

Acked-by: Vlastimil Babka <vbabka@suse.cz>

> ---
>  mm/workingset.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/mm/workingset.c b/mm/workingset.c
> index 10e96de945b3..7db8f3dad13c 100644
> --- a/mm/workingset.c
> +++ b/mm/workingset.c
> @@ -461,6 +461,8 @@ static unsigned long count_shadow_nodes(struct shrinker *shrinker,
>  	unsigned long pages;
>  
>  	nodes = list_lru_shrink_count(&shadow_nodes, sc);
> +	if (!nodes)
> +		return SHRINK_EMPTY;
>  
>  	/*
>  	 * Approximate a reasonable limit for the nodes
> @@ -503,9 +505,6 @@ static unsigned long count_shadow_nodes(struct shrinker *shrinker,
>  
>  	max_nodes = pages >> (XA_CHUNK_SHIFT - 3);
>  
> -	if (!nodes)
> -		return SHRINK_EMPTY;
> -
>  	if (nodes <= max_nodes)
>  		return 0;
>  	return nodes - max_nodes;
> 



      reply	other threads:[~2021-01-26 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-23  7:38 Miaohe Lin
2021-01-26 16:24 ` Vlastimil Babka [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=8dea8eff-3100-4f57-5d61-e532803d256f@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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