|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] Scheduling traffic based on Vif interfaces on xen dom0 using DRR
Hi
i am using tc tools on dom0 to schedule traffic that comes from
different guests using Deficit Round Robin scheduling algorithm. Here
is my scenario:
eth0------| bridge |--------------+----- vif1.0 domU 1
| |
| +----- vif2.0 domU 2
dom0 |
+----- vif3.0 domU 3
|
+ ... ... ... ... ...
|
+------ vif10.0 domU 10
And i use this config:
#1
tc add qdisc add dev eth0 handle 1 root drr
#2
tc class add dev eth0 parent 1: classid1:1 drr quantum 3000
tc class add dev eth0 parent 1: classid1:2 drr quantum 1500
tc class add dev eth0 parent 1: classid1:3 drr quantum 3000
... ... ... .... ... .... ....
.... .... .... ..
tc class add dev eth0 parent 1: classid1:10 drr quantum 3000
#3
iptables -t mangle -A FORWARD -m physdev --physdev-in vif1.0 -j MARK
--set-mark 1
iptables -t mangle -A FORWARD -m physdev --physdev-in vif2.0 -j MARK
--set-mark 2
iptables -t mangle -A FORWARD -m physdev --physdev-in vif3.0 -j MARK
--set-mark 3
... ... ... .... ... .... ....
.... .... .... ..
iptables -t mangle -A FORWARD -m physdev --physdev-in vif10.0 -j MARK
--set-mark 10
#4
tc filter add dev eth0 protocol ip parent 1: handle 2 fw flowid 1:1
tc filter add dev eth0 protocol ip parent 1: handle 3 fw flowid 1:2
tc filter add dev eth0 protocol ip parent 1: handle 4 fw flowid 1:3
... ... ... .... ... .... ....
.... .... .... ..
tc filter add dev eth0 protocol ip parent 1: handle 11 fw flowid 1:10
############
the first problem is that as i just enter the first command to create
a root drr qdisc the dom0 and other guest can not be reachable outside
eth0, while inside interdomain communication is ok.
Which is the problem?
Thanks
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |