All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Ryo Tsuruta <ryov@valinux.co.jp>
Cc: kvm-devel@lists.sourceforge.net, dm-devel@redhat.com,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: I/O bandwidth control on KVM
Date: Sat, 01 Mar 2008 22:18:03 -0600	[thread overview]
Message-ID: <47CA2A7B.8000400@codemonkey.ws> (raw)
In-Reply-To: <20080229.210531.226799765.ryov__28298.7898834564$1204287044$gmane$org@valinux.co.jp>

Hi Ryo,

Ryo Tsuruta wrote:
> Hello all,
> 
> I've implemented a block device which throttles block I/O bandwidth, 
> which I called dm-ioband, and been trying to throttle I/O bandwidth on
> KVM environment. But unfortunately it doesn't work well, the number of
> issued I/Os is not according to the bandwidth setting.
> On the other hand, I got the good result when accessing directly to
> the local disk on the local machine.
> 
> I'm not so familiar with KVM. Could anyone give me any advice?

If you are using virtio drivers in the guest (which I presume you are 
given the reference to /dev/vda), try using the following -drive syntax:

-drive file=/dev/mapper/ioband1,if=virtio,boot=on,cache=off

This will force the use of O_DIRECT.  By default, QEMU does not open 
with O_DIRECT so you'll see page cache effects.

Regards,

Anthony Liguori

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-03-02  4:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 12:05 I/O bandwidth control on KVM Ryo Tsuruta
2008-03-02  4:18 ` Anthony Liguori
2008-03-02  4:18 ` Anthony Liguori [this message]
2008-03-02 16:45   ` Avi Kivity
2008-03-02 16:45   ` Avi Kivity
2008-03-02 18:08     ` Anthony Liguori
2008-03-02 18:08     ` Anthony Liguori
2008-03-04  6:41   ` Ryo Tsuruta
2008-03-05 15:53     ` [kvm-devel] " Ryo Tsuruta
2008-03-05 16:30       ` Anthony Liguori
2008-03-06 12:23         ` Ryo Tsuruta
2008-03-06 12:23         ` Ryo Tsuruta
2008-03-06 16:05           ` [kvm-devel] " Anthony Liguori
2008-03-06 16:05           ` Anthony Liguori
2008-03-10 12:05             ` Ryo Tsuruta
2008-03-10 12:05             ` [kvm-devel] " Ryo Tsuruta
2008-03-05 16:30       ` Anthony Liguori
2008-03-05 15:53     ` Ryo Tsuruta
2008-03-04  6:41   ` Ryo Tsuruta
  -- strict thread matches above, loose matches on Subject: below --
2008-02-29 12:05 Ryo Tsuruta

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=47CA2A7B.8000400@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=dm-devel@redhat.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=ryov@valinux.co.jp \
    --cc=virtualization@lists.linux-foundation.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.