From: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: "Kirill A. Shutsemov" <kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
Cc: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
Arjan van de Ven <arjan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Matt Helsley <matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH, v7] cgroups: introduce timer slack controller
Date: Wed, 2 Mar 2011 19:40:01 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1103021912090.2701@localhost6.localdomain6> (raw)
In-Reply-To: <1299084001-3916-2-git-send-email-kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
On Wed, 2 Mar 2011, Kirill A. Shutsemov wrote:
Not CC'ing me does not avoid another review :)
> diff --git a/fs/select.c b/fs/select.c
> index e56560d..a189e4d 100644
> --- a/fs/select.c
> +++ b/fs/select.c
> @@ -69,7 +69,6 @@ static long __estimate_accuracy(struct timespec *tv)
>
> long select_estimate_accuracy(struct timespec *tv)
> {
> - unsigned long ret;
> struct timespec now;
>
> /*
> @@ -81,10 +80,8 @@ long select_estimate_accuracy(struct timespec *tv)
>
> ktime_get_ts(&now);
> now = timespec_sub(*tv, now);
> - ret = __estimate_accuracy(&now);
> - if (ret < current->timer_slack_ns)
> - return current->timer_slack_ns;
> - return ret;
> + return clamp(__estimate_accuracy(&now),
> + get_task_timer_slack(current), LONG_MAX);
> }
Can you please split out the get_task_timer_slack() change into a
separate patch?
Also the function wants to be named different.
task_get_effective_timer_slack() or such, so it becomes clear, that
it's not just a wrapper around tsk->timer_slack_ns
And the places which access tsk->timer_slack_ns directly should be
updated with comments, why they are not using the wrapper.
> +static int tslack_write_min(struct cgroup *cgroup, struct cftype *cft, u64 val)
> +{
> + struct cgroup *cur;
> +
> + if (val > ULONG_MAX)
> + return -EINVAL;
> +
> + /* the min timer slack value should be more or equal than parent's */
s/should/must/
> + if (cgroup->parent) {
> + struct tslack_cgroup *parent = cgroup_to_tslack(cgroup->parent);
New line between variables and code please
> + if (parent->min_slack_ns > val)
> + return -EPERM;
> + }
> +
> + cgroup_to_tslack(cgroup)->min_slack_ns = val;
> +
> + /* update children's min slack value if needed */
> + list_for_each_entry(cur, &cgroup->children, sibling) {
> + struct tslack_cgroup *child = cgroup_to_tslack(cur);
Ditto
> + if (val > child->min_slack_ns)
> + tslack_write_min(cur, cft, val);
> + }
So, we can increase the value and propagate it through the groups
children, but decreasing it requires to go through all child groups
seperately.
When I'm trying to optimize something during runtime and chose a too
high value I need to go through hoops and loops to make it smaller
again.
Asymetric behaviour sucks always.
> +unsigned long get_task_timer_slack(struct task_struct *tsk)
> +{
> + struct cgroup_subsys_state *css;
> + struct tslack_cgroup *tslack_cgroup;
> + unsigned long ret;
> +
> + rcu_read_lock();
Did you just remove the odd comment or actually figure out why you
need rcu_read_lock() here ?
> + css = task_subsys_state(tsk, timer_slack_subsys.subsys_id);
> + tslack_cgroup = container_of(css, struct tslack_cgroup, css);
> + ret = max(tsk->timer_slack_ns, tslack_cgroup->min_slack_ns);
> + rcu_read_unlock();
> +
> + return ret;
> +}
Otherwise, it's way more palatable than the last one.
Thanks,
tglx
next prev parent reply other threads:[~2011-03-02 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 16:40 [PATCH, v7] Introduce timer slack controller Kirill A. Shutsemov
[not found] ` <1299084001-3916-1-git-send-email-kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
2011-03-02 16:40 ` [PATCH, v7] cgroups: introduce " Kirill A. Shutsemov
[not found] ` <1299084001-3916-2-git-send-email-kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org>
2011-03-02 18:40 ` Thomas Gleixner [this message]
[not found] ` <alpine.LFD.2.00.1103021912090.2701-bi+AKbBUZKagILUCTcTcHdKyNwTtLsGr@public.gmane.org>
2011-03-03 6:59 ` Li Zefan
[not found] ` <4D6F3C5B.8020307-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2011-03-03 7:34 ` Thomas Gleixner
2011-03-03 7:46 ` Matt Helsley
[not found] ` <20110303074609.GL14893-52DBMbEzqgQ/wnmkkaCWp/UQ3DHhIser@public.gmane.org>
2011-03-03 8:28 ` Thomas Gleixner
2011-03-03 8:33 ` Kirill A. Shutemov
2011-03-04 19:03 ` Peter Zijlstra
2011-03-04 23:22 ` 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=alpine.LFD.2.00.1103021912090.2701@localhost6.localdomain6 \
--to=tglx-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=arjan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jacob.jun.pan-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=kirill-oKw7cIdHH8eLwutG50LtGA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
--cc=matthltc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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