From: MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>
To: akpm@osdl.org, linux-kernel@vger.kernel.org,
ckrm-tech@lists.sourceforge.net
Cc: MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>
Subject: [PATCH 0/9] CPU controller
Date: Fri, 28 Apr 2006 10:37:30 +0900 [thread overview]
Message-ID: <20060428013730.9582.9351.sendpatchset@moscone.dvs.cs.fujitsu.co.jp> (raw)
Andrew,
This patchset adds a CPU resource controller on top of Resource Groups.
The CPU resource controller manages CPU resources by scaling timeslice
allocated for each task without changing the algorithm of the O(1)
scheduler.
Please consider these for inclusion in -mm tree.
--
Patch descriptions:
1/9: cpurc_load_estimation
- Adds class load estimation support
2/9: cpurc_hungry_detection
- Adds class hungry detection support
3/9: cpurc_timeslice_scaling
- Adds CPU resource controll by scaling timeslice
4/9: cpurc_interface
- Adds interface functions to CKRM CPU controller
5/9: cpurc_docs
- Documentation how the CPU resource controller works
6/9: cpu_init
- Adds the basic functions and registering the CPU controller
on top of Resource Groups
7/9: cpu_shares_n_stats
- Adds routines to change share values and show statistics
8/9: cpu_hotplug
- Adds cpu hotplug support
9/9: cpu_docs
- Documentation how to use the CPU controller
Thanks,
MAEDA Naoaki
next reply other threads:[~2006-04-28 1:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 1:37 MAEDA Naoaki [this message]
2006-04-28 1:37 ` [PATCH 1/9] CPU controller - Add class load estimation support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 2/9] CPU controller - Add class hungry detection support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 3/9] CPU controller - Add timeslice scaling support MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 4/9] CPU controller - Add interface functions MAEDA Naoaki
2006-04-28 1:37 ` [PATCH 5/9] CPU controller - Documentation how the controller works MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 6/9] CPU controller - Add basic functions and registering the controller MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 7/9] CPU controller - Add routines to change share values and show stat MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 8/9] CPU controller - Add cpu hotplug support MAEDA Naoaki
2006-04-28 1:38 ` [PATCH 9/9] CPU controller - Documentation how to use the controller MAEDA Naoaki
2006-04-28 5:25 ` [PATCH 0/9] CPU controller Mike Galbraith
2006-04-28 5:48 ` MAEDA Naoaki
2006-04-28 6:59 ` Mike Galbraith
2006-04-28 7:26 ` MAEDA Naoaki
2006-04-28 7:41 ` Mike Galbraith
2006-04-28 7:56 ` [ckrm-tech] " MAEDA Naoaki
2006-04-28 9:29 ` Mike Galbraith
2006-04-28 10:01 ` Mike Galbraith
2006-04-28 10:11 ` Con Kolivas
2006-04-28 12:07 ` MAEDA Naoaki
2006-04-28 13:09 ` Con Kolivas
2006-04-28 13:55 ` Hirokazu Takahashi
2006-04-28 14:55 ` Con Kolivas
2006-04-28 15:39 ` Mike Galbraith
2006-04-28 5:56 ` Kirill Korotaev
2006-04-28 7:11 ` Mike Galbraith
2006-04-28 7:46 ` Mike Galbraith
2006-04-28 8:13 ` Kirill Korotaev
2006-04-28 9:35 ` Mike Galbraith
2006-04-28 10:09 ` Con Kolivas
2006-04-28 10:16 ` Mike Galbraith
2006-04-28 10:26 ` Con Kolivas
2006-04-28 10:42 ` Mike Galbraith
2006-04-28 8:28 ` MAEDA Naoaki
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=20060428013730.9582.9351.sendpatchset@moscone.dvs.cs.fujitsu.co.jp \
--to=maeda.naoaki@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-kernel@vger.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