linux-kernel - Re: [PATCH v2] memcg: first step towards hierarchical controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 4 Sep 2012 18:37:53 +0400
From:	Glauber Costa <glommer@...allels.com>
To:	Michal Hocko <mhocko@...e.cz>
CC:	<linux-kernel@...r.kernel.org>, <cgroups@...r.kernel.org>,
	<linux-mm@...ck.org>, Dave Jones <davej@...hat.com>,
	Ben Hutchings <ben@...adent.org.uk>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Turner <pjt@...gle.com>,
	Lennart Poettering <lennart@...ttering.net>,
	Kay Sievers <kay.sievers@...y.org>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Johannes Weiner <hannes@...xchg.org>, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v2] memcg: first step towards hierarchical controller

On 09/04/2012 06:35 PM, Michal Hocko wrote:
> On Tue 04-09-12 17:27:20, Glauber Costa wrote:
>> On 09/04/2012 05:09 PM, Michal Hocko wrote:
>>> Not really. Do it slowly means that somebody actually _notices_ that
>>> something is about to change and they have a lot of time for that. This
>>> will be really hard with the config option saying N by default.  People
>>> will ignore that until it's too late.
>>> We are interested in those users who would keep the config default N and
>>> they are (ab)using use_hierarchy=0 in a way which is hard/impossible to
>>> fix. This is where distributions might help and they should IMHO but why
>>> to put an additional code into upstream? Isn't it sufficient that those
>>> who would like to help (and take the risk) would just take the patch?
>>
>> At least Fedora, seem to frown upon heavily at non-upstream patches.
> 
> OK, so what about the following approach instead? We won't change the
> default but rather shout at people when they actually create subtrees
> with use_hierarchy==0. This shouldn't make pointless noise. I do not
> remember whether we have considered this previously so sorry if this was
> shot down as well.

The warning is fine, but just shouting won't achieve nothing. I believe
it would be really great to have a way to turn the default to 1 - and
stop the shouting.

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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/