From: Glauber Costa <glommer@parallels.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-mm@kvack.org, Dave Jones <davej@redhat.com>,
Ben Hutchings <ben@decadent.org.uk>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Turner <pjt@google.com>,
Lennart Poettering <lennart@poettering.net>,
Kay Sievers <kay.sievers@vrfy.org>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v2] memcg: first step towards hierarchical controller
Date: Tue, 4 Sep 2012 18:54:08 +0400 [thread overview]
Message-ID: <50461610.30305@parallels.com> (raw)
In-Reply-To: <20120904145414.GC15683@dhcp22.suse.cz>
>> I believe it would be really great to have a way to turn the default
>> to 1 - and stop the shouting.
>
> We already can. You can use /etc/cgconfig (if you are using libcgroup)
> or do it manually.
>
>> Even if you are doing it in OpenSUSE as a patch, an upstream patch means
>> at least that every distribution is using the same patch, and those who
>> rebase will just flip the config.
>>
>> I'd personally believe merging both our patches together would achieve a
>> good result.
>
> I am still not sure we want to add a config option for something that is
> meant to go away. But let's see what others think.
>
So what you propose in the end is that we add a userspace tweak for
something that could go away, instead of a Kconfig for something that go
away.
Way I see it, Kconfig is better because it is totally transparent, under
the hood, and will give us a single location to unpatch in case/when it
really goes away.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-09-04 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 15:46 Glauber Costa
2012-09-03 16:41 ` Ben Hutchings
2012-09-04 8:29 ` Glauber Costa
2012-09-03 17:08 ` Michal Hocko
2012-09-04 8:34 ` Glauber Costa
2012-09-04 13:09 ` Michal Hocko
2012-09-04 13:27 ` Glauber Costa
2012-09-04 14:35 ` Michal Hocko
2012-09-04 14:37 ` Glauber Costa
2012-09-04 14:54 ` Michal Hocko
2012-09-04 14:54 ` Glauber Costa [this message]
2012-09-04 16:25 ` Michal Hocko
2012-09-05 8:14 ` Glauber Costa
2012-09-05 14:49 ` Michal Hocko
2012-09-05 20:12 ` Tejun Heo
2012-09-06 12:06 ` Michal Hocko
2012-09-06 12:09 ` Glauber Costa
2012-09-06 12:18 ` Michal Hocko
2012-09-07 9:45 ` Glauber Costa
2012-09-04 18:22 ` Tejun Heo
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=50461610.30305@parallels.com \
--to=glommer@parallels.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ben@decadent.org.uk \
--cc=cgroups@vger.kernel.org \
--cc=davej@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kay.sievers@vrfy.org \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=pjt@google.com \
--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