All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Pitcock <nenolod@dereferenced.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/2] blkback: Add default policy values for I/O	QoS code
Date: Tue, 31 Mar 2009 07:25:01 -0500	[thread overview]
Message-ID: <1238502301.5814.86.camel@petrie> (raw)
In-Reply-To: <49D1C4CD.70404@goop.org>

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

      parent reply	other threads:[~2009-03-31 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  2:53 [PATCH 0/2] RFC: Implement I/O QoS in dom0 William Pitcock
2009-03-31  2:12 ` [PATCH 1/2] blkback: Implement VBD QoS mechanics William Pitcock
2009-03-31  2:38 ` [PATCH 2/2] blkback: Add default policy values for I/O QoS code William Pitcock
2009-03-31  7:22   ` Jeremy Fitzhardinge
2009-03-31  8:12     ` Ian Campbell
2009-03-31 12:25     ` William Pitcock [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=1238502301.5814.86.camel@petrie \
    --to=nenolod@dereferenced.org \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.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 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.