public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: T Johnson <tjohnson46@gmail.com>
Cc: kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: limiting guest block i/o for qos
Date: Thu, 25 Nov 2010 09:33:18 +0100	[thread overview]
Message-ID: <20101125083318.GA2398@nik-comp.lan> (raw)
In-Reply-To: <AANLkTi=FdV6KOeL2D9r-at3yR1AfajSDC78ao5aOOuzV@mail.gmail.com>

Hello Thomas,
I t hink blkio-cgroup really can't help You here, but since NFS is
network protocol,
why not just consider some kind of network shaping?
n.

On Thu, Nov 25, 2010 at 12:58:22AM -0500, T Johnson wrote:
> Hello,
> 
> Does anyone know of any work in progress or any tricks to limit a
> guest's i/o requests to a specific throttled rate? I have guests that
> mount their filesystems via virtio, which are images served on an NFS
> server. Some of these guests will flood the server with requests and
> can then choke out the i/o requests of neighboring guests. I'd rather
> be able to specify that certain guests can only get so many read or
> write iops. i/o bandwidth rates would be nice, but iops tend to be the
> killer since an nfs server only has so many.
> 
> I've seen something recently on a block i/o throttling via cgroups,
> but from what I've been able to grok... this support is being built
> only with local devices in mind? I'm afraid that wouldn't work for my
> NFS server setup and image files?
> 
> Is there something that can be done from with virtio? Or another trick?
> 
> Thanks,
> Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2010-11-25  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25  5:58 limiting guest block i/o for qos T Johnson
2010-11-25  8:33 ` Nikola Ciprich [this message]
2010-11-29  2:00   ` T Johnson
2010-11-29  9:58     ` Stefan Hajnoczi
2010-11-30  0:57       ` T Johnson

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=20101125083318.GA2398@nik-comp.lan \
    --to=extmaillist@linuxbox.cz \
    --cc=kvm@vger.kernel.org \
    --cc=nikola.ciprich@linuxbox.cz \
    --cc=tjohnson46@gmail.com \
    /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