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
Subject: Re: [PATCH 1/2] Traffic control cgroups subsystem
Date: Mon, 21 Jul 2008 17:26:41 +0800 [thread overview]
Message-ID: <48845651.4010904@cn.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807181425270.18212@ranjit.corp.google.com>
Ranjit Manomohan wrote:
> This patch adds a traffic control cgroup subsystem that is used
> to tag all packets originating from tasks in this cgroup with a
> specific identifier (tc_classid).
>
> Signed-off-by: Ranjit Manomohan <ranjitm@google.com>
>
> ---
>
> diff --git a/include/linux/cgroup_subsys.h b/include/linux/cgroup_subsys.h
> index e287745..4b12372 100644
> --- a/include/linux/cgroup_subsys.h
> +++ b/include/linux/cgroup_subsys.h
> @@ -48,3 +48,9 @@ SUBSYS(devices)
> #endif
>
> /* */
> +
> +#ifdef CONFIG_CGROUP_TC
> +SUBSYS(tc)
> +#endif
> +
seems tc is not a good name... I won't know it stands for traffic-control if I
didn't know beforehand.
> +int cgroup_tc_classid(struct task_struct *tsk)
> +{
> + rcu_read_lock();
> + return container_of(task_subsys_state(tsk, tc_subsys_id),
> + struct tc_cgroup, css)->classid;
> + rcu_read_unlock();
How do you unlock after return ;)
> +}
> +
> +static struct cgroup_subsys_state *tc_create(struct cgroup_subsys *ss,
> + struct cgroup *cgroup)
> +{
> + struct tc_cgroup *tc_cgroup;
> +
> + tc_cgroup = kzalloc(sizeof(*tc_cgroup), GFP_KERNEL);
> +
The 'if (!tc_cgroup)' below should be here.
> + /* Copy parent's class id if present */
> + if (cgroup->parent)
> + tc_cgroup->classid = cgroup_to_tc(cgroup->parent)->classid;
> +
> + if (!tc_cgroup)
> + return ERR_PTR(-ENOMEM);
> + return &tc_cgroup->css;
> +}
next prev parent reply other threads:[~2008-07-21 9:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 21:28 [PATCH 1/2] Traffic control cgroups subsystem Ranjit Manomohan
2008-07-21 9:26 ` Li Zefan [this message]
2008-07-21 14:04 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2008-07-24 23:35 Ranjit Manomohan
2008-08-22 0:55 Ranjit Manomohan
2008-08-22 2:11 ` Li Zefan
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
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=48845651.4010904@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--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