From: Li Zefan <lizf@cn.fujitsu.com>
To: Ranjit Manomohan <ranjitm@google.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
menage@google.com, kaber@trash.net, akpm@linux-foundation.org
Subject: Re: [PATCH 1/2] Traffic control cgroups subsystem
Date: Fri, 22 Aug 2008 10:11:27 +0800 [thread overview]
Message-ID: <48AE204F.307@cn.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0808211753360.23590@ranjit.corp.google.com>
> +static unsigned int cgroup_tc_classid(struct task_struct *tsk)
> +{
> + unsigned int tc_classid;
> +
> + rcu_read_lock();
> + tc_classid = container_of(task_subsys_state(tsk, tc_subsys_id),
trivial: 2 spaces ^^
> + struct tc_cgroup, css)->classid;
> + rcu_read_unlock();
> + return tc_classid;
> +}
> +
...
> +static int tc_write_u64(struct cgroup *cgrp, struct cftype *cft, u64 val)
> +{
> + struct tc_cgroup *tc = cgroup_to_tc(cgrp);
> +
> + cgroup_lock();
> + if (cgroup_is_removed(cgrp)) {
> + cgroup_unlock();
> + return -ENODEV;
> + }
> +
You may use cgroup_lock_live_group():
if (cgroup_lock_live_group(cgrp0))
return -ENODEV;
> + tc->classid = (unsigned int) (val & 0xffffffff);
> + cgroup_unlock();
> + return 0;
> +}
> +
> +static u64 tc_read_u64(struct cgroup *cont, struct cftype *cft)
'cont', 'cgrp' and 'cgroup' are used, it's better to make it consistent
to use 'cgrp' (or 'cgroup') only.
> +{
> + struct tc_cgroup *tc = cgroup_to_tc(cont);
> + return tc->classid;
> +}
next prev parent reply other threads:[~2008-08-22 2:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 0:55 [PATCH 1/2] Traffic control cgroups subsystem Ranjit Manomohan
2008-08-22 2:11 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-10 17:42 Ranjit Manomohan
2008-09-10 22:01 ` Thomas Graf
2008-09-10 22:56 ` Ranjit Manomohan
2008-09-10 23:00 ` David Miller
2008-09-10 23:14 ` Ranjit Manomohan
2008-09-10 23:04 ` Paul Menage
2008-09-10 23:24 ` Thomas Graf
2008-09-10 23:31 ` Paul Menage
2008-09-10 23:45 ` Thomas Graf
2008-09-10 23:51 ` Paul Menage
2008-09-11 0:07 ` Thomas Graf
2008-09-11 0:09 ` Paul Menage
2008-09-10 23:53 ` Paul Menage
2008-07-24 23:35 Ranjit Manomohan
2008-07-18 21:28 Ranjit Manomohan
2008-07-21 9:26 ` Li Zefan
2008-07-21 14:04 ` Patrick McHardy
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=48AE204F.307@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=netdev@vger.kernel.org \
--cc=ranjitm@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;
as well as URLs for NNTP newsgroup(s).