From: Ben Hutchings <ben@decadent.org.uk>
To: Michal Hocko <mhocko@suse.cz>
Cc: Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
cgroups@vger.kernel.org,
Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: Re: [PATCH] mm, memcg: Optionally disable memcg by default using Kconfig
Date: Tue, 19 May 2015 18:09:52 +0100 [thread overview]
Message-ID: <1432055392.12412.34.camel@decadent.org.uk> (raw)
In-Reply-To: <20150519151541.GJ6203@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1994 bytes --]
On Tue, 2015-05-19 at 17:15 +0200, Michal Hocko wrote:
> [Let's CC Ben here - the email thread has started here:
> http://marc.info/?l=linux-mm&m=143203206402073&w=2 and it seems Debian
> is disabling memcg controller already so this might be of your interest]
>
> On Tue 19-05-15 15:43:45, Mel Gorman wrote:
> [...]
> > After I wrote the patch, I spotted that Debian apparently already
> > does something like this and by coincidence they matched the
> > parameter name and values. See the memory controller instructions on
> > https://wiki.debian.org/LXC#Prepare_the_host . So in this case at least
> > upstream would match something that at least one distro in the field
> > already uses.
>
> I've read through
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534964 and it seems
> that the primary motivation for the runtime disabling was the _memory_
> overhead of the struct page_cgroup
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534964#152). This is
> no longer the case since 1306a85aed3e ("mm: embed the memcg pointer
> directly into struct page") merged in 3.19.
>
> I can see some point in disabling the memcg due to runtime overhead.
I was also concerned about runtime overhead.
> There will always be some, albeit hard to notice. If an user really need
> this to happen there is a command line option for that. The question is
> who would do CONFIG_MEMCG && !MEMCG_DEFAULT_ENABLED. Do you expect any
> distributions go that way?
> Ben, would you welcome such a change upstream or is there a reason to
> change the Debian kernel runtime default now that the memory overhead is
> mostly gone (for 3.19+ kernels of course)?
I have been meaning to reevaluate this as I know the overhead has been
reduced. Given Mel's benchmark results, I favour keeping it disabled by
default in Debian. So I would welcome this change.
Ben.
--
Ben Hutchings
I'm not a reverse psychological virus. Please don't copy me into your sig.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-05-19 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 10:40 [PATCH] mm, memcg: Optionally disable memcg by default using Kconfig Mel Gorman
2015-05-19 14:18 ` Johannes Weiner
2015-05-19 14:43 ` Mel Gorman
2015-05-19 15:15 ` Michal Hocko
2015-05-19 17:09 ` Ben Hutchings [this message]
2015-05-19 14:53 ` Michal Hocko
2015-05-19 15:12 ` Vlastimil Babka
2015-05-19 15:13 ` Mel Gorman
2015-05-19 15:25 ` Vlastimil Babka
2015-05-19 16:14 ` Johannes Weiner
2015-05-19 15:27 ` Michal Hocko
2015-05-19 15:41 ` Mel Gorman
2015-05-19 16:04 ` Mel Gorman
2015-05-19 19:32 ` Mel Gorman
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=1432055392.12412.34.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=debian-kernel@lists.debian.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=tj@kernel.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