Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-06 Thread Balbir Singh
On Tue, Aug 6, 2013 at 7:39 PM, Tejun Heo wrote: > Hello, Balbir. > > On Tue, Aug 06, 2013 at 08:56:34AM +0530, Balbir Singh wrote: >> [off-topic] Has the unified hierarchy been agreed upon? I did not >> follow that thread > > I consider it agreed upon enough. There of course are objections but

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-06 Thread Tejun Heo
Hello, Balbir. On Tue, Aug 06, 2013 at 08:56:34AM +0530, Balbir Singh wrote: > [off-topic] Has the unified hierarchy been agreed upon? I did not > follow that thread I consider it agreed upon enough. There of course are objections but I feel fairly comfortable with the amount of existing

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-06 Thread Tejun Heo
Hello, Balbir. On Tue, Aug 06, 2013 at 08:56:34AM +0530, Balbir Singh wrote: [off-topic] Has the unified hierarchy been agreed upon? I did not follow that thread I consider it agreed upon enough. There of course are objections but I feel fairly comfortable with the amount of existing

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-06 Thread Balbir Singh
On Tue, Aug 6, 2013 at 7:39 PM, Tejun Heo t...@kernel.org wrote: Hello, Balbir. On Tue, Aug 06, 2013 at 08:56:34AM +0530, Balbir Singh wrote: [off-topic] Has the unified hierarchy been agreed upon? I did not follow that thread I consider it agreed upon enough. There of course are

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-05 Thread Balbir Singh
On Sun, Aug 4, 2013 at 9:37 PM, Tejun Heo wrote: > cgroup_event is way over-designed and tries to build a generic > flexible event mechanism into cgroup - fully customizable event > specification for each user of the interface. This is utterly > unnecessary and overboard especially in the light

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-05 Thread Balbir Singh
On Sun, Aug 4, 2013 at 9:37 PM, Tejun Heo t...@kernel.org wrote: cgroup_event is way over-designed and tries to build a generic flexible event mechanism into cgroup - fully customizable event specification for each user of the interface. This is utterly unnecessary and overboard especially in

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-04 Thread Li Zefan
于 2013/8/5 0:07, Tejun Heo 写道: > cgroup_event is way over-designed and tries to build a generic > flexible event mechanism into cgroup - fully customizable event > specification for each user of the interface. This is utterly > unnecessary and overboard especially in the light of the planned >

[PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-04 Thread Tejun Heo
cgroup_event is way over-designed and tries to build a generic flexible event mechanism into cgroup - fully customizable event specification for each user of the interface. This is utterly unnecessary and overboard especially in the light of the planned unified hierarchy as there's gonna be

[PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-04 Thread Tejun Heo
cgroup_event is way over-designed and tries to build a generic flexible event mechanism into cgroup - fully customizable event specification for each user of the interface. This is utterly unnecessary and overboard especially in the light of the planned unified hierarchy as there's gonna be

Re: [PATCH 3/5] cgroup, memcg: move cgroup_event implementation to memcg

2013-08-04 Thread Li Zefan
于 2013/8/5 0:07, Tejun Heo 写道: cgroup_event is way over-designed and tries to build a generic flexible event mechanism into cgroup - fully customizable event specification for each user of the interface. This is utterly unnecessary and overboard especially in the light of the planned unified