[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] 4.1 feature request: block device throttling/scheduling

  • To: Pasi Kärkkäinen <pasik@xxxxxx>
  • From: T Johnson <tjohnson46@xxxxxxxxx>
  • Date: Fri, 9 Apr 2010 19:46:10 -0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 09 Apr 2010 16:47:06 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Pwrf1c35MAloGIkZuEmdIVf9QnQ+LxtLE5Du+e5M2qLKuWVl4OkW2KBNvlyRjx3NP6 L0S0kCnePq6KiMs0bpsb3s83JLkQh7H3AzZNocMFRZJDHOd0tWk+gAV++VCNsvq3/3AS 66jF4rdNp/rJAuamq3VtZLEugvVfVWP2Ei9Pg=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


On Fri, Apr 9, 2010 at 12:47 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
On Fri, Apr 09, 2010 at 12:13:32PM -0400, T Johnson wrote:

>    In an ideal world I could specify that vmX can perform Y writes per second
>    and Z reads per second (since sometimes reads can be less expensive than
>    writes)
>
>    Please let me know if you have any questions. Adding something like this
>    in would be *greatly* appreciated.
>

Did you take a look at dm-ioband?


I did, but unless I'm missing something it doesn't work too well for storage networks (especially NFS) when you're using
file-backed block devices. Also, I'd rather have limits on the ops/sec rather than just prioritization.   

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.