[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1346768300-10282-1-git-send-email-glommer@parallels.com>
Date: Tue, 4 Sep 2012 18:18:15 +0400
From: Glauber Costa <glommer@...allels.com>
To: <linux-kernel@...r.kernel.org>
Cc: <cgroups@...r.kernel.org>, <linux-mm@...ck.org>, davej@...hat.com,
ben@...adent.org.uk, a.p.zijlstra@...llo.nl, pjt@...gle.com,
lennart@...ttering.net, kay.sievers@...y.org, tj@...nel.org
Subject: [RFC 0/5] forced comounts for cgroups.
Hi,
As we have been extensively discussing, the cost and pain points for cgroups
come from many places. But at least one of those is the arbitrary nature of
hierarchies. Many people, including at least Tejun and me would like this to go
away altogether. Problem so far, is breaking compatiblity with existing setups
I am proposing here a default-n Kconfig option that will guarantee that the cpu
cgroups (for now) will be comounted. I started with them because the
cpu/cpuacct division is clearly the worst offender. Also, the default-n is here
so distributions will have time to adapt: Forcing this flag to be on without
userspace changes will just lead to cgroups failing to mount, which we don't
want.
Although I've tested it and it works, I haven't compile-tested all possible
config combinations. So this is mostly for your eyes. If this gets traction,
I'll submit it properly, along with any changes that you might require.
Thanks.
Glauber Costa (5):
cgroup: allow some comounts to be forced.
sched: adjust exec_clock to use it as cpu usage metric
sched: do not call cpuacct_charge when cpu and cpuacct are comounted
cpuacct: do not gather cpuacct statistics when not mounted
sched: add cpusets to comounts list
include/linux/cgroup.h | 6 ++
init/Kconfig | 23 ++++++++
kernel/cgroup.c | 29 +++++++++-
kernel/cpuset.c | 4 ++
kernel/sched/core.c | 149 +++++++++++++++++++++++++++++++++++++++++++++----
kernel/sched/rt.c | 1 +
kernel/sched/sched.h | 20 ++++++-
7 files changed, 220 insertions(+), 12 deletions(-)
--
1.7.11.4
--
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/
Powered by blists - more mailing lists