From: Randy Dunlap <randy.dunlap@oracle.com>
To: vatsa@linux.vnet.ibm.com
Cc: akpm@linux-foundation.org, Ingo Molnar <mingo@elte.hu>,
dmitry.adamushko@gmail.com, efault@gmx.de,
dhaval@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
containers@lists.osdl.org
Subject: Re: [PATCH -mm] Hook up group scheduler with control groups
Date: Thu, 27 Sep 2007 10:40:05 -0700 [thread overview]
Message-ID: <20070927104005.2ed0b81d.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070927150624.GG4415@linux.vnet.ibm.com>
On Thu, 27 Sep 2007 20:36:24 +0530 Srivatsa Vaddagiri wrote:
> Andrew,
> This is a resend of the patch I had sent earlier at:
>
> http://marc.info/?l=linux-kernel&m=119065506607858
>
> This patch enables group cpu scheduler feature to work with control
> groups.
>
> Could you include this in -mm for folks to test it?
Hi :)
Uh, a few of my previous comments weren't fixed... (below)
> --
>
> Enable "cgroup" (formerly containers) based fair group scheduling.
> This will let administrator create arbitrary groups of tasks (using
> "cgroup" pseudo filesystem) and control their cpu bandwidth usage.
>
> Signed-off-by : Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
> Signed-off-by : Dhaval Giani <dhaval@linux.vnet.ibm.com>
>
> ---
> include/linux/cgroup_subsys.h | 6 ++
> init/Kconfig | 24 +++++---
> kernel/sched.c | 122 ++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 145 insertions(+), 7 deletions(-)
>
> Index: current/init/Kconfig
> ===================================================================
> --- current.orig/init/Kconfig
> +++ current/init/Kconfig
> @@ -319,6 +319,13 @@ config CPUSETS
>
> Say N if unsure.
>
> +config RESOURCE_COUNTERS
> + bool "Resource counters"
> + help
> + This option enables controller independent resource accounting
> + infrastructure that works with cgroups
Use tab + 2 spaces consistently for help text indentation.
End that sentence with a ".".
> + depends on CGROUPS
> +
> config FAIR_GROUP_SCHED
> bool "Fair group CPU scheduler"
> default y
---
~Randy
Phaedrus says that Quality is about caring.
next prev parent reply other threads:[~2007-09-27 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 15:06 [PATCH -mm] Hook up group scheduler with control groups Srivatsa Vaddagiri
2007-09-27 17:40 ` Randy Dunlap [this message]
2007-09-27 18:04 ` Dhaval Giani
2007-09-27 19:00 ` Randy Dunlap
2007-09-27 19:35 ` Dhaval Giani
2007-09-27 23:42 ` Andrew Morton
2007-09-28 2:40 ` Srivatsa Vaddagiri
-- strict thread matches above, loose matches on Subject: below --
2007-09-27 19:41 Frans Pop
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=20070927104005.2ed0b81d.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=dmitry.adamushko@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
/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