linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: xiakaixu1987@gmail.com
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com, linux-mm@kvack.org,
	Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH] mm: memcontrol: simplify value comparison between count and limit
Date: Tue, 21 Apr 2020 16:59:56 +0200	[thread overview]
Message-ID: <20200421145956.GJ27314@dhcp22.suse.cz> (raw)
In-Reply-To: <1587479661-27237-1-git-send-email-kaixuxia@tencent.com>

On Tue 21-04-20 22:34:21, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
> 
> When the variables count and limit have the same value(count == limit),
> the result of min(margin, limit - count) statement should be 0 and the
> variable margin is set to 0. So in this case, the min() statement is not
> necessary and we can directly set the variable margin to 0.

I expect that the compiler would generate the same code but there is no
reason to differ in memsw branch from the main limit check so the patch
looks ok to me.

> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>

 Acked-by: Michal Hocko <mhocko@suse.com>

> ---
>  mm/memcontrol.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 5beea03dd58a..fedc5afdc482 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1314,7 +1314,7 @@ static unsigned long mem_cgroup_margin(struct mem_cgroup *memcg)
>  	if (do_memsw_account()) {
>  		count = page_counter_read(&memcg->memsw);
>  		limit = READ_ONCE(memcg->memsw.max);
> -		if (count <= limit)
> +		if (count < limit)
>  			margin = min(margin, limit - count);
>  		else
>  			margin = 0;
> -- 
> 2.20.0

-- 
Michal Hocko
SUSE Labs


      reply	other threads:[~2020-04-21 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 14:34 [PATCH] mm: memcontrol: simplify value comparison between count and limit xiakaixu1987
2020-04-21 14:59 ` Michal Hocko [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=20200421145956.GJ27314@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kaixuxia@tencent.com \
    --cc=linux-mm@kvack.org \
    --cc=vdavydov.dev@gmail.com \
    --cc=xiakaixu1987@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;
as well as URLs for NNTP newsgroup(s).