From: Ranjit Manomohan <ranjitm@google.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: menage@google.com
Subject: [PATCH 0/2] Traffic control cgroups subsystem
Date: Fri, 18 Jul 2008 14:25:18 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0807181420230.18212@ranjit.corp.google.com> (raw)
This set of patches 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 new traffic control classifier (cls_cgroup) that can classify packets
based on the tc_classid field in the packet to specific destination classes.
A simple example of the use of this resource controller would be to limit
the traffic from all tasks from a file_server cgroup to 100Mbps. We could
achieve this by doing:
# make a cgroup of file transfer processes and assign it a uniqe classid
# of 0x1234
mkdir -p /dev/cgroup
mount -t cgroup tc -otc /dev/cgroup
mkdir /dev/cgroup/file_transfer
echo 0x1234 > /dev/cgroup/file_transfer/tc.classid
echo $PID_OF_FILE_XFER_PROCESS > /dev/cgroup/file_transfer/tasks
# Now create a HTB class that rate limits traffic to 100mbits and attach
# a filter to direct all traffic from cgroup file_transfer to this new class.
tc qdisc add dev eth0 root handle 1: htb
tc class add dev eth0 parent 1: classid 1:2 htb rate 100mbit ceil 100mbit
tc filter add dev eth0 parent 1: protocol ip prio 1 handle 800 cgroup value 0x1234 classid 1:2
Signed-off-by: Ranjit Manomohan <ranjitm@google.com>
---
next reply other threads:[~2008-07-18 21:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 21:25 Ranjit Manomohan [this message]
2008-08-22 0:53 Ranjit Manomohan
2008-09-10 17:40 Ranjit Manomohan
2008-09-10 20:22 ` David Miller
2008-09-10 20:44 ` Ranjit Manomohan
2008-09-10 22:12 ` Thomas Graf
2008-09-10 23:37 ` Ranjit Manomohan
2008-09-10 23:52 ` Thomas Graf
2008-09-26 1:07 김재열
2008-09-26 6:16 김재열
2008-09-26 9:57 ` Chen Zumeng
2008-10-15 13:03 ` Chen Zumeng
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=Pine.LNX.4.64.0807181420230.18212@ranjit.corp.google.com \
--to=ranjitm@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=netdev@vger.kernel.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
Powered by JetHome