From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Paul Menage <menage@google.com>
Cc: Li Zefan <lizf@cn.fujitsu.com>,
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>
Subject: Re: [PATCH, v3 2/2] cgroups: introduce timer slack subsystem
Date: Thu, 3 Feb 2011 11:28:55 +0200 [thread overview]
Message-ID: <20110203092855.GC1083@shutemov.name> (raw)
In-Reply-To: <AANLkTikAbmFmQNGgYMYhTOS8L5nU39edcTjQXNpdxGy2@mail.gmail.com>
On Wed, Feb 02, 2011 at 03:23:15PM -0800, Paul Menage wrote:
> On Wed, Feb 2, 2011 at 12:47 PM, Kirill A. Shutsemov
> <kirill@shutemov.name> wrote:
> > From: Kirill A. Shutemov <kirill@shutemov.name>
> >
> > Provides a way of tasks grouping by timer slack value. Introduces per
> > cgroup max and min timer slack value. When a task attaches to a cgroup,
> > its timer slack value adjusts (if needed) to fit min-max range.
> >
> > It also provides a way to set timer slack value for all tasks in the
> > cgroup at once.
> >
> > This functionality is useful in mobile devices where certain background
> > apps are attached to a cgroup and minimum wakeups are desired.
>
> If you really want to be able to make this modular,
Why not?
> I'd be inclined to
> make the check_timer_slack hook just default to NULL, rather than
> introducing dummy_timer_slack_check()
Good point.
> > +
> > +static int tslack_write_range(struct cgroup *cgroup, struct cftype *cft,
> > + u64 val)
> > +{
> > + struct timer_slack_cgroup *tslack_cgroup;
> > + struct cgroup_iter it;
> > + struct task_struct *task;
> > +
> > + if (!val)
> > + return -EINVAL;
> > +
> > + tslack_cgroup = cgroup_to_tslack_cgroup(cgroup);
> > + switch (cft->private) {
> > + case TIMER_SLACK_MIN:
> > + if (val > tslack_cgroup->max_slack_ns)
> > + return -EINVAL;
> > + tslack_cgroup->min_slack_ns = val;
> > + break;
> > + case TIMER_SLACK_MAX:
> > + if (val < tslack_cgroup->min_slack_ns)
> > + return -EINVAL;
> > + tslack_cgroup->max_slack_ns = val;
> > + break;
> > + default:
> > + BUG();
> > + }
> > +
>
> Don't we want to keep the min/max applied hierarchically as well? i.e.
> a child can't set its min/max outside the range of its parents?
Ok, I'll implement it.
> > +
> > +static int __init init_cgroup_timer_slack(void)
> > +{
> > + BUG_ON(timer_slack_check != dummy_timer_slack_check);
>
> Better to make this just fail the initialization if someone else has
> already claimed the hook, rather than crashing.
Ok.
Thanks, for reviewing.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2011-02-03 9:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 20:47 [PATCH, v3 0/2] Timer slack cgroup subsystem Kirill A. Shutsemov
2011-02-02 20:47 ` [PATCH, v3 1/2] cgroups: export cgroup_iter_{start,next,end} Kirill A. Shutsemov
2011-02-02 21:21 ` Paul Menage
2011-02-02 20:47 ` [PATCH, v3 2/2] cgroups: introduce timer slack subsystem Kirill A. Shutsemov
2011-02-02 22:56 ` jacob pan
2011-02-03 9:22 ` Kirill A. Shutemov
2011-02-03 17:51 ` Jacob Pan
2011-02-03 18:12 ` Paul Menage
2011-02-03 19:57 ` Jacob Pan
2011-02-04 13:34 ` Kirill A. Shutemov
2011-02-04 17:27 ` Jacob Pan
2011-02-07 0:33 ` Matt Helsley
2011-02-07 11:06 ` Kirill A. Shutemov
2011-02-07 17:20 ` Jacob Pan
2011-02-07 18:32 ` Kirill A. Shutemov
2011-02-02 23:23 ` Paul Menage
2011-02-03 5:48 ` Matt Helsley
2011-02-03 9:28 ` Kirill A. Shutemov [this message]
2011-02-03 5:46 ` Matt Helsley
2011-02-03 9:41 ` Kirill A. Shutemov
2011-02-06 2:49 ` Matt Helsley
2011-02-07 9:48 ` Kirill A. Shutemov
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=20110203092855.GC1083@shutemov.name \
--to=kirill@shutemov.name \
--cc=arjan@linux.intel.com \
--cc=containers@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=matthltc@us.ibm.com \
--cc=menage@google.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