WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 2/2] blkback: Add default policy values for I/O Q

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/2] blkback: Add default policy values for I/O QoS code
From: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Date: Tue, 31 Mar 2009 07:25:01 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 31 Mar 2009 05:25:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <49D1C4CD.70404@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <cover.1238468013.git.nenolod@xxxxxxxxxxxxxxxx> <9d22c2b519c198454814a1011283144b3736627b.1238468013.git.nenolod@xxxxxxxxxxxxxxxx> <49D1C4CD.70404@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2009-03-31 at 00:22 -0700, Jeremy Fitzhardinge wrote:
> William Pitcock wrote:
> > This patch adds default values which define a default QoS policy for
> > guest I/O. A sysctl interface will be added once /proc/sys/xen is available
> > again... unless I come up with a better idea in the meantime.
> >   
> 
> What would that interface look like?  Would the parameters be per 
> domain, or per device?  Would sysfs be suitable?

I was thinking about sysfs as an option, but xenstore also seems
desirable, since that way we can integrate QoS policy directly into the
vm config in an easy way without having to modify the userland tools in
any sort of major way.

Ian mentioned that netback uses xenstore for getting information, so I
think we could do the same here to get the QoS policy. It seems like a
sensible way.

Also, hopefully the dom0 base stuff will make it for 2.6.30. Can't wait
to have pvops-dom0 in production... keeping my fingers crossed on that
one. Although I could just backport this work to 2.6.18-xen.hg if it
comes down to being necessary to do so.

William



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