All of lore.kernel.org
 help / color / mirror / Atom feed
From: jacob.jun.pan@linux.intel.com
To: LKML <linux-kernel@vger.kernel.org>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Matt Helsley <matthltc@us.ibm.com>,
	container cgroup <containers@lists.linux-foundation.org>,
	Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>,
	akpm@linux-foundation.org, rdunlap@xenotime.net,
	Cedric Le Goater <clg@fr.ibm.com>
Cc: Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: [PATCH 0/1, v9] cgroup/freezer: add per freezer duty ratio control
Date: Tue, 15 Feb 2011 14:09:09 -0800	[thread overview]
Message-ID: <1297807750-28844-1-git-send-email-jacob.jun.pan@linux.intel.com> (raw)

From: Jacob Pan <jacob.jun.pan@linux.intel.com>

Fixing subject in cover letter, should be v4 instead of v3

Changelog:
v9:	- merged duty ratio related data structs
	- removed toggling bit, replaced with freezer->state
	- consolidated toggling mode cancellation function	
	- use spin lock to protect duty ratio parameter writes
	- use second as period
	- allow 0% and 100% frozen time, aligned behavior with
	  freezer_write()
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(-)


             reply	other threads:[~2011-02-15 22:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 22:09 jacob.jun.pan [this message]
2011-02-15 22:09 ` [PATCH 1/1, v9] cgroup/freezer: add per freezer duty ratio control jacob.jun.pan
2011-02-16  0:00   ` Rafael J. Wysocki
     [not found]     ` <201102160100.15487.rjw-KKrjLPT3xs0@public.gmane.org>
2011-02-16  0:38       ` Jacob Pan
2011-02-16  0:38     ` Jacob Pan
2011-02-16  3:23       ` Matt Helsley
2011-02-16  3:23       ` Matt Helsley
2011-02-16  3:23       ` Matt Helsley
2011-02-16 18:18         ` Jacob Pan
2011-02-16 18:18         ` Jacob Pan
     [not found]         ` <20110216032321.GA14893-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2011-02-16 18:18           ` Jacob Pan
2011-02-24 23:45           ` jacob pan
2011-02-24 23:45         ` jacob pan
2011-02-24 23:45         ` jacob pan
2011-02-25 17:53           ` Paul Menage
2011-02-25 17:53           ` Paul Menage
     [not found]             ` <AANLkTinyhp29X8-atA=0DaHFuthTjVMJgBOitP52gwEX-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-25 18:23               ` Jacob Pan
2011-02-25 18:23             ` Jacob Pan
2011-02-25 18:23             ` Jacob Pan
2011-02-25 17:53           ` Paul Menage
2011-02-16  0:38     ` Jacob Pan
2011-02-16  0:00   ` Rafael J. Wysocki
     [not found]   ` <1297807750-28844-2-git-send-email-jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2011-02-16  0:00     ` Rafael J. Wysocki
     [not found] ` <1297807750-28844-1-git-send-email-jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2011-02-15 22:09   ` jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA
  -- strict thread matches above, loose matches on Subject: below --
2011-02-15 22:09 [PATCH 0/1, " jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA

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=1297807750-28844-1-git-send-email-jacob.jun.pan@linux.intel.com \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=clg@fr.ibm.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=matthltc@us.ibm.com \
    --cc=menage@google.com \
    --cc=rdunlap@xenotime.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.