[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1297455745-15841-1-git-send-email-jacob.jun.pan@linux.intel.com>
Date: Fri, 11 Feb 2011 12:22:25 -0800
From: jacob.jun.pan@...ux.intel.com
To: LKML <linux-kernel@...r.kernel.org>,
"Kirill A. Shutemov" <kirill@...temov.name>,
Arjan van de Ven <arjan@...ux.intel.com>,
Matt Helsley <matthltc@...ibm.com>,
container cgroup <containers@...ts.linux-foundation.org>,
Li Zefan <lizf@...fujitsu.com>,
Paul Menage <menage@...gle.com>, akpm@...ux-foundation.org,
rdunlap@...otime.net, Cedric Le Goater <clg@...ibm.com>
Cc: Jacob Pan <jacob.jun.pan@...ux.intel.com>
Subject: [PATCH 0/1, v8] cgroup/freezer: add per freezer duty ratio control
From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
Fixing subject in cover letter, should be v4 instead of v3
Changelog:
v8: - minor clean up
v7: - use delayed workqueue instead of per cgroup kernel thread
to manage toggling
- make freezer.state higher priority than duty ratio setting
- small correction in documentation
v6: - remove check for duty ratio == 100 case
v5: - improve error handling in duty ratio/ period writes
- fix the logic to avoid kthread creation when ratio and
period are invalid.
- 100% frozen is not permitted in duty ratio set up
v4: - limit kthread creation only when valid duty ratio
parameters are given.
- changed period back to milisecond
- consolidated paramter write functions
v3: - added documentation
v2:
- use read_u64/write_u64 instead of string read/write
- use period in second instead of ms
- renamed duty_ratio to duty_ratio_pct, be more specific
- removed locking around period and duty_ratio reads
Jacob Pan (1):
cgroup/freezer: add per freezer duty ratio control
Documentation/cgroups/freezer-subsystem.txt | 23 ++++++
kernel/cgroup_freezer.c | 109 ++++++++++++++++++++++++++-
2 files changed, 130 insertions(+), 2 deletions(-)
--
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