From: Li Zefan <lizf@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Kirill A. Shutsemov" <kirill@shutemov.name>,
Paul Menage <menage@google.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>,
Andrew Morton <akpm@linux-foundation.org>,
linux-api@vger.kernel.org
Subject: Re: [PATCH, v7] cgroups: introduce timer slack controller
Date: Thu, 03 Mar 2011 14:59:39 +0800 [thread overview]
Message-ID: <4D6F3C5B.8020307@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1103021912090.2701@localhost6.localdomain6>
>> +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 ?
>
It's necessary to protect against task exiting or task moving between cgroups.
>> + 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-03 6:57 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
2011-03-02 16:40 ` [PATCH, v7] cgroups: introduce " Kirill A. Shutsemov
2011-03-02 18:40 ` Thomas Gleixner
2011-03-03 6:59 ` Li Zefan [this message]
2011-03-03 7:34 ` Thomas Gleixner
2011-03-03 7:46 ` Matt Helsley
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=4D6F3C5B.8020307@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=containers@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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