From: Bharata B Rao <bharata@linux.ibm.com>
To: Michal Hocko <mhocko@suse.com>
Cc: Dave Chinner <david@fromorbit.com>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
aneesh.kumar@linux.ibm.com
Subject: Re: High kmalloc-32 slab cache consumption with 10k containers
Date: Thu, 15 Apr 2021 12:51:30 +0530 [thread overview]
Message-ID: <20210415072130.GA1749436@in.ibm.com> (raw)
In-Reply-To: <YHfjMyJuvXzJsg6T@dhcp22.suse.cz>
On Thu, Apr 15, 2021 at 08:54:43AM +0200, Michal Hocko wrote:
> On Thu 15-04-21 10:53:00, Bharata B Rao wrote:
> > On Wed, Apr 07, 2021 at 08:28:07AM +1000, Dave Chinner wrote:
> > >
> > > Another approach may be to identify filesystem types that do not
> > > need memcg awareness and feed that into alloc_super() to set/clear
> > > the SHRINKER_MEMCG_AWARE flag. This could be based on fstype - most
> > > virtual filesystems that expose system information do not really
> > > need full memcg awareness because they are generally only visible to
> > > a single memcg instance...
> >
> > Would something like below be appropriate?
>
> No. First of all you are defining yet another way to say
> SHRINKER_MEMCG_AWARE which is messy.
Ok.
> And secondly why would shmem, proc
> and ramfs be any special and they would be ok to opt out? There is no
> single word about that reasoning in your changelog.
Right, I am only checking if the suggestion given by David (see above)
is indeed this. There are a few other things to take care of
which I shall if the overall direction of the patch turns
out to be acceptable.
Regards,
Bharata.
next prev parent reply other threads:[~2021-04-15 7:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 5:48 High kmalloc-32 slab cache consumption with 10k containers Bharata B Rao
2021-04-05 8:22 ` kernel test robot
2021-04-05 8:22 ` kernel test robot
2021-04-05 18:08 ` Yang Shi
2021-04-05 18:08 ` Yang Shi
2021-04-05 18:38 ` Roman Gushchin
2021-04-06 10:13 ` Bharata B Rao
2021-04-06 10:05 ` Bharata B Rao
2021-04-07 1:39 ` Yang Shi
2021-04-07 1:39 ` Yang Shi
2021-04-06 22:28 ` Dave Chinner
2021-04-07 5:05 ` Bharata B Rao
2021-04-07 10:07 ` Kirill Tkhai
2021-04-07 11:47 ` Bharata B Rao
2021-04-07 12:49 ` Kirill Tkhai
2021-04-07 13:57 ` Christian Brauner
2021-04-15 5:23 ` Bharata B Rao
2021-04-15 6:54 ` Michal Hocko
2021-04-15 7:21 ` Bharata B Rao [this message]
2021-04-16 4:44 ` Bharata B Rao
2021-04-19 1:23 ` Dave Chinner
2021-04-07 11:54 ` Michal Hocko
2021-04-07 13:32 ` Christian Brauner
2021-04-07 13:43 ` Bharata B Rao
2021-04-07 13:57 ` Michal Hocko
2021-04-07 15:42 ` Shakeel Butt
2021-04-07 15:42 ` Shakeel Butt
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=20210415072130.GA1749436@in.ibm.com \
--to=bharata@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.