From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>
Cc: containers@lists.linux-foundation.org,
jacob.jun.pan@linux.intel.com,
Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org, Matt Helsley <matthltc@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-api@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH, v8 0/3] *** SUBJECT HERE ***
Date: Thu, 3 Mar 2011 16:20:30 +0200 [thread overview]
Message-ID: <20110303142030.GA9980@shutemov.name> (raw)
In-Reply-To: <1299161947-9903-1-git-send-email-kirill@shutemov.name>
On Thu, Mar 03, 2011 at 04:19:04PM +0200, Kirill A. Shutsemov wrote:
> From: Kirill A. Shutemov <kirill@shutemov.name>
>
> *** BLURB HERE ***
Oops.
Changelog:
v8:
- change hiearchy rules
- introduce timer_slack.effective_slack_ns
- get_task_timer_slack() -> task_get_effective_timer_slack()
- task_get_effective_timer_slack() splited in separate patch
- implement PR_GET_EFFECTIVE_TIMERSLACK
v7:
- totally reworked interface and rewritten from scratch
(See Documentation/cgroups/timer_slack.txt for more information)
v6:
- add documentation
- use notifier_call_chain() instead of check hook
- fix validate_change()
- cleanup
v5:
- -EBUSY on writing to timer_slack.min_slack_ns/max_slack_ns if a child has
wider min-max range
v4:
- hierarchy support
- drop dummy_timer_slack_check()
- workaround lockdep false (?) positive
- allow 0 as timer slack value
v3:
- rework interface
- s/EXPORT_SYMBOL/EXPORT_SYMBOL_GPL/
v2:
- fixed with CONFIG_CGROUP_TIMER_SLACK=y
v1:
- initial revision
> Kirill A. Shutemov (3):
> hrtimer: introduce effective timer slack
> hrtimer: implement PR_GET_EFFECTIVE_TIMERSLACK
> cgroups: introduce timer slack controller
>
> Documentation/cgroups/timer_slack.txt | 64 +++++++++++++++++
> fs/select.c | 7 +--
> include/linux/cgroup_subsys.h | 6 ++
> include/linux/prctl.h | 6 ++
> include/linux/sched.h | 10 +++
> init/Kconfig | 8 ++
> kernel/Makefile | 1 +
> kernel/cgroup_timer_slack.c | 124 +++++++++++++++++++++++++++++++++
> kernel/fork.c | 4 +
> kernel/futex.c | 4 +-
> kernel/hrtimer.c | 2 +-
> kernel/sys.c | 3 +
> 12 files changed, 231 insertions(+), 8 deletions(-)
> create mode 100644 Documentation/cgroups/timer_slack.txt
> create mode 100644 kernel/cgroup_timer_slack.c
>
> --
> 1.7.4.1
>
--
Kirill A. Shutemov
prev parent reply other threads:[~2011-03-03 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 14:19 [PATCH, v8 0/3] *** SUBJECT HERE *** Kirill A. Shutsemov
2011-03-03 14:19 ` [PATCH, v8 1/3] hrtimer: introduce effective timer slack Kirill A. Shutsemov
2011-03-03 16:32 ` Arnd Bergmann
2011-03-04 12:20 ` Kirill A. Shutemov
2011-03-04 12:55 ` Arnd Bergmann
2011-03-03 14:19 ` [PATCH, v8 2/3] hrtimer: implement PR_GET_EFFECTIVE_TIMERSLACK Kirill A. Shutsemov
2011-03-03 14:19 ` [PATCH, v8 3/3] cgroups: introduce timer slack controller Kirill A. Shutsemov
2011-03-07 23:19 ` Andrew Morton
2011-03-03 14:20 ` Kirill A. Shutemov [this message]
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=20110303142030.GA9980@shutemov.name \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=containers@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthltc@us.ibm.com \
--cc=menage@google.com \
--cc=tglx@linutronix.de \
/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