From: Rick Jones <rick.jones2@hp.com>
To: netdev@vger.kernel.org, kvm@vger.kernel.org
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Brian Haley <Brian.Haley@hp.com>
Subject: NIC emulation with built-in rate limiting?
Date: Tue, 11 Sep 2012 11:07:07 -0700 [thread overview]
Message-ID: <504F7DCB.3050401@hp.com> (raw)
Are there NIC emulations in the kernel with built-in rate limiting? Or
is that supposed to be strictly the province of qdiscs/filters?
I've been messing about with netperf in a VM using virtio_net, to which
rate limiting has been applied to its corresponding vnetN interface -
rate policing on vnetN ingress (the VM's outbound) and htb on the vnetN
egress (the VM's inbound).
Looking at the "demo mode" output of netperf and a VM throttled to 800
Mbit/s in each direction I see that inbound to the VM is quite steady
over time - right at about 800 Mbit/s. However, looking at that same
sort of data for outbound from the VM shows considerable variability
ranging anywhere from 700 to 900 Mbit/s (though the bulk of the
variability is clustered more like 750 to 850.
I was thinking that part of the reason may stem from the lack of direct
feedback to the VM since the policing is on the vnetN interface and
wondered if it might be "better" if the VM's outbound network rate were
constrained not by an ingress policing filter on the vnetN interface but
by the host/hypervisor/emulator portion of the NIC and how quickly it
pulls packets from the tx queue. That would allow the queue which
built-up to be in the VM itself and would more accurately represent what
a "real NIC" of that bandwidth would do.
happy benchmarking,
rick jones
next reply other threads:[~2012-09-11 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:07 Rick Jones [this message]
2012-09-11 19:05 ` NIC emulation with built-in rate limiting? Gregory Carter
2012-09-17 21:48 ` Rick Jones
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=504F7DCB.3050401@hp.com \
--to=rick.jones2@hp.com \
--cc=Brian.Haley@hp.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=kvm@vger.kernel.org \
--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