linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Shakeel Butt <shakeelb@google.com>, Roman Gushchin <guro@fb.com>,
	Lorenzo Stoakes <lstoakes@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Alexander Duyck <alexander.h.duyck@linux.intel.com>,
	Yafang Shao <laoar.shao@gmail.com>,
	Wei Yang <richard.weiyang@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memcg: bail out early when !memcg in mem_cgroup_lruvec
Date: Fri, 27 Nov 2020 20:02:15 -0800	[thread overview]
Message-ID: <20201127200215.dc96a839cdd816361e7093e6@linux-foundation.org> (raw)
In-Reply-To: <1606446515-36069-1-git-send-email-alex.shi@linux.alibaba.com>

On Fri, 27 Nov 2020 11:08:35 +0800 Alex Shi <alex.shi@linux.alibaba.com> wrote:

> Sometime, we use NULL memcg in mem_cgroup_lruvec(memcg, pgdat)
> so we could get out early in the situation to avoid useless checking.
> 
> Also warning if both parameter are NULL.

Why do you think a warning is needed here?

> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -613,14 +613,13 @@ static inline struct lruvec *mem_cgroup_lruvec(struct mem_cgroup *memcg,
>  	struct mem_cgroup_per_node *mz;
>  	struct lruvec *lruvec;
>  
> -	if (mem_cgroup_disabled()) {
> +	VM_WARN_ON_ONCE(!memcg && !pgdat);
> +
> +	if (mem_cgroup_disabled() || !memcg) {
>  		lruvec = &pgdat->__lruvec;
>  		goto out;
>  	}
>  
> -	if (!memcg)
> -		memcg = root_mem_cgroup;
> -

This change isn't obviously equivalent, is it?

>  	mz = mem_cgroup_nodeinfo(memcg, pgdat->node_id);
>  	lruvec = &mz->lruvec;
>  out:

And the resulting code is awkward:

	if (mem_cgroup_disabled() || !memcg) {
		lruvec = &pgdat->__lruvec;
		goto out;
	}

	mz = mem_cgroup_nodeinfo(memcg, pgdat->node_id);
	lruvec = &mz->lruvec;
out:


could be

	if (mem_cgroup_disabled() || !memcg) {
		lruvec = &pgdat->__lruvec;
	} else {
		mem_cgroup_per_node mz;

		mz = mem_cgroup_nodeinfo(memcg, pgdat->node_id);
		lruvec = &mz->lruvec;
	}


  reply	other threads:[~2020-11-28  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27  3:08 [PATCH] mm/memcg: bail out early when !memcg in mem_cgroup_lruvec Alex Shi
2020-11-28  4:02 ` Andrew Morton [this message]
2020-11-29  4:43   ` Alex Shi
2020-11-30 19:44     ` Dmitry Osipenko
2020-11-30 20:19       ` Andrew Morton

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=20201127200215.dc96a839cdd816361e7093e6@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alex.shi@linux.alibaba.com \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=laoar.shao@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lstoakes@gmail.com \
    --cc=richard.weiyang@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=shakeelb@google.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).