From: "Daniel P. Berrange" <berrange@redhat.com>
To: Pradeep Kiruvale <pradeepkiruvale@gmail.com>
Cc: Alberto Garcia <berto@igalia.com>,
qemu-devel@nongnu.org,
"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-discuss] Throttle in virtio-net
Date: Tue, 6 Sep 2016 15:37:03 +0100 [thread overview]
Message-ID: <20160906143703.GM10095@redhat.com> (raw)
In-Reply-To: <CAJ2SuLnFoLab+GqakO-F1Yss1ebeRzKjjjJGxtOM7XDuzBCJKg@mail.gmail.com>
On Mon, Sep 05, 2016 at 10:52:40AM +0200, Pradeep Kiruvale wrote:
> Hi Alberto,
>
> Thanks for your reply.
>
> >
> > > I am planning to implement throttling functionality for virtio-net
> > > driver using the throttling APIs that exist inside qemu.
> >
> > Hi Pradeep,
> >
> > the problem with implementing throttling for the network is that
> > it's useless if you use the vhost_net kernel accelerator, because it
> > bypasses QEMU entirely:
> >
> > https://access.redhat.com/documentation/en-US/Red_Hat_
> > Enterprise_Linux/7/html/Virtualization_Tuning_and_Optimization_Guide/sect-
> > Virtualization_Tuning_Optimization_Guide-Networking-
> > Virtio_and_vhostnet.html
>
>
> Thanks for this very valuable information. What if someone wants to just
> use virtio-net without the vhost acceleration?
> Any idea how it will be done in this case? It still uses cgroup or some
> other mechanism to do throttling?
>
> >
> > libvirt implements this using tc:
> >
> > https://libvirt.org/formatdomain.html#elementDomain
> > http://luxik.cdi.cz/~devik/qos/htb/manual/userg.htm#ceiling
>
>
> Here it uses the cgroup inside the libvirt dirver to control the packet
> rate right?
No, cgroups is not involved. Libvirt attaches a tc filter directly to
the host TAP device associated with the virtual NIC.
Cgroups tc support would only be relevant if you're trying to filter
non-NIC related network traffic QEMU generates.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-09-06 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 15:13 [Qemu-devel] Throttle in virtio-net Pradeep Kiruvale
2016-09-05 8:33 ` [Qemu-devel] [Qemu-discuss] " Alberto Garcia
2016-09-05 8:52 ` Pradeep Kiruvale
2016-09-06 14:10 ` Alberto Garcia
2016-09-06 14:37 ` Daniel P. Berrange [this message]
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=20160906143703.GM10095@redhat.com \
--to=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=pradeepkiruvale@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.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.