linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, mhocko@kernel.org, hannes@cmpxchg.org,
	vdavydov.dev@gmail.com, akpm@linux-foundation.org
Subject: Re: [PATCH] mm/list_lru: dont make them memcg aware if kmem is disabled
Date: Fri, 27 Nov 2020 20:21:11 +1100	[thread overview]
Message-ID: <20201127092111.GA473773@balbir-desktop> (raw)
In-Reply-To: <a23d12ad-d45e-01d2-8978-d0ebe9afb39a@suse.cz>

On Thu, Nov 26, 2020 at 01:10:18PM +0100, Vlastimil Babka wrote:
> On 11/26/20 5:30 AM, Balbir Singh wrote:
> > When alloc_super() allocates list_lrus for dentries and inodes
> > they are made memcg aware if KMEM is compiled in, we should
> > also check if kmem was disabled at runtime.
> > 
> > This overhead is about 32 bytes extra per possible nodes per caller
> > of list_lru_init()
> > 
> > Signed-off-by: Balbir Singh <bsingharora@gmail.com>
> 
> I'd rather export cgroup_memory_nokmem and make cgroup_kmem_disabled()
> inline, put it next to memcg_kmem_enabled() and explain in comments what
> each means.
> 
> And ideally, the current memcg_kmem_enabled() should be named e.g.
> memcg_kmem_active(), and then the new cgroup_kmem_disabled() could be named
> memcg_kmem_enabled(). But that's churn and potential future backport hazard,
> so dunno.

Yes, I am happy with whatever approach works to fast track the patches

Andrew, thoughts/comments?

Balbir Singh.


  reply	other threads:[~2020-11-27  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26  4:30 [PATCH] mm/list_lru: dont make them memcg aware if kmem is disabled Balbir Singh
2020-11-26 12:10 ` Vlastimil Babka
2020-11-27  9:21   ` Balbir Singh [this message]
2020-11-28  3:49     ` Andrew Morton
2020-11-28 11:47       ` Balbir Singh

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=20201127092111.GA473773@balbir-desktop \
    --to=bsingharora@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=vdavydov.dev@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).