From: Patrick McHardy <kaber@trash.net>
To: Ranjit Manomohan <ranjitm@google.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
lizf@cn.fujitsu.com, menage@google.com
Subject: Re: [PATCH] Traffic control cgroups subsystem
Date: Tue, 22 Jul 2008 12:35:09 +0200 [thread overview]
Message-ID: <4885B7DD.7070507@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0807212100580.1760@ranjit.corp.google.com>
Ranjit Manomohan wrote:
>
> [Take 2] - Incorporated comments from Patric McHardy & Li Zefan.
>
> This patch provides a simple resource controller (cgroup_tc) based on the
> cgroups infrastructure to manage network traffic. The cgroup_tc resource
> controller can be used to schedule and shape traffic belonging to the
> task(s)
> in a particular cgroup.
>
> The implementation consists of two parts:
>
> 1) A resource controller (cgroup_tc) that is used to associate packets from
> a particular task belonging to a cgroup with a traffic control class
> id (
> tc_classid). This tc_classid is propagated to all sockets created by
> tasks
> in the cgroup and from there to all packets associated with those
> sockets.
>
> 2) A modified traffic control classifier (cls_flow) that can classify
> packets
> based on the tc_classid field in the packet to specific destination
> classes.
Does this really have to be a new skb member? You could
simply use skb->sk->sk_cgroup_classid directly, or if
that doesn't work, maybe skb->priority.
next prev parent reply other threads:[~2008-07-22 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 4:08 [PATCH] Traffic control cgroups subsystem Ranjit Manomohan
2008-07-22 10:35 ` Patrick McHardy [this message]
2008-07-22 12:14 ` Paul Menage
2008-07-22 12:48 ` Patrick McHardy
2008-07-22 12:56 ` Paul Menage
-- strict thread matches above, loose matches on Subject: below --
2008-07-22 17:44 Ranjit Manomohan
2008-07-23 22:05 ` Andrew Morton
2008-07-23 22:34 ` Patrick McHardy
2008-07-23 23:54 ` Ranjit Manomohan
2008-07-24 0:17 ` Patrick McHardy
2008-07-24 23:45 ` Thomas Graf
2008-07-25 1:16 ` Ranjit Manomohan
2008-07-25 9:29 ` Thomas Graf
2008-07-25 1:18 ` 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=4885B7DD.7070507@trash.net \
--to=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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).