From: "Neil Aggarwal" <neil@JAMMConsulting.com>
To: lartc@vger.kernel.org
Subject: Poor performance of ingress filter for separate VMs
Date: Wed, 08 May 2013 18:11:29 +0000 [thread overview]
Message-ID: <000f01ce4c17$76dfa490$649eedb0$@JAMMConsulting.com> (raw)
Hello everyone:
I have a CentOS server running two virtual machines using KVM.
Each machine has its own virtual device since I am using bridged
networking.
I am trying to allocate bandwidth to each virtual machine using tc.
I have these rules set up:
/sbin/tc qdisc add dev v1262 ingress handle ffff:
/sbin/tc filter add dev v1262 parent ffff: protocol ip prio 50 u32 match ip
src 0.0.0.0/0 police rate 5mbit burst 500k mtu 3100 drop flowid :1
/sbin/tc qdisc add dev v1263 ingress handle ffff:
/sbin/tc filter add dev v1263 parent ffff: protocol ip prio 50 u32 match ip
src 0.0.0.0/0 police rate 5mbit burst 500k mtu 3100 drop flowid :1
You can see them when I do a qdisc ls:
qdisc ingress ffff: dev v1262 parent ffff:fff1 ----------------
qdisc ingress ffff: dev v1263 parent ffff:fff1 ----------------
The problem is when v1262 is doing a large upload, v1263 gets starved.
If I remove the ingress qdisc, v1263 runs at full speed regardless of what
v1262 is doing.
Its as if the two devices are using the same queue. I did not think that
would happen since
they are totally separate devices.
Any ideas what is happening here?
Thanks,
Neil
--
Neil Aggarwal, (972)834-1565, http://UnmeteredVPS.net/centos
Virtual private server with CentOS 6 preinstalled
Unmetered bandwidth = no overage charges
next reply other threads:[~2013-05-08 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 18:11 Neil Aggarwal [this message]
2013-05-09 10:17 ` Poor performance of ingress filter for separate VMs Andy Furniss
2013-05-09 11:00 ` Andy Furniss
2013-05-10 16:45 ` Neil Aggarwal
2013-05-10 20:37 ` Andy Furniss
2013-05-10 23:40 ` Neil Aggarwal
2013-05-11 11:41 ` Andy Furniss
2013-05-11 14:59 ` Neil Aggarwal
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='000f01ce4c17$76dfa490$649eedb0$@JAMMConsulting.com' \
--to=neil@jammconsulting.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.