All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Florian Heigl <florian.heigl@gmail.com>
Cc: Shaun Reitan <mailinglists@unix-scripts.com>,
	xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: Re: VM disk I/O limit patch
Date: Tue, 28 Jun 2011 09:29:57 -0400	[thread overview]
Message-ID: <20110628132957.GC7777@dumpdata.com> (raw)
In-Reply-To: <BANLkTinvx+Gv6cD0=8NpqqFApke2HTmYFA@mail.gmail.com>

On Tue, Jun 28, 2011 at 01:32:14PM +0200, Florian Heigl wrote:
> Hi Konrad,
> 
> Thanks for providing links to info about both dm-ioband and bklio.
> This is surely something to test with and might be the best choice for
> Xen from 2.6.34 and up.
> 
> Question/food for thought:
> since:
> - 2.6.18 still has CFQ1 which has notable issues with processes
> starving each other (some people have seen this and some havent, but
> it exists and it's one of the worst issues that exist. Normally people
> will switch to deadline scheduler and ... experience they no longer
> can priorize now, and even then they'll still see their dom0 go
> sluggish if a domU is too IO heavy)
> - Both blkio patch and dm-ioband are not in 2.6.18 and not even in 2.6.32(!!!)

Right, so you can upgrade to 3.0 or 2.6.39.

> - The patch from last week was for 2.618...

Ah, not idea who is the maintainer for the 2.6.18 tree anymore.

> 
> would it be possible to add the patch to the 2.6.18-ish Xen trees and
> not into the 3.x one?

You are welcome to do this, but I don't think anybody else is going to do this.
I am definitly not going to take the patch for the 3.0 tree.

> We could have a (hopefully) working solution for a problem that exists
> now on the deployments that are in use now and that could easily go
> into a XenServer 5.6 Patch123456 or XCP or OracleVM.
> 
> 
> This might also be the more time-conserving way to do it, since right
> now the cgroups mechanisms in Linux are nice, but it should be obvious
> that there's still a year or two to go from setting up every single
> stuff via /sys after a process is started to a working solution that
> can be pre-configured for all VMs.
> 
> Unless anybody thinks this is enough ;)
> 
> 
> 2011/6/27 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
> > On Thu, Jun 23, 2011 at 01:45:36PM -0700, Shaun Reitan wrote:
> >> Does this match only limit throughput or can it also limit the guest
> >> by disk IOPS?  christopher aker had a patch way back for UML that
> >
> > Just throughpout.
> >
> >> did disk based qos.  What i really liked about that patch was that
> >> it allowed for bursting by using a bucket.  If i remember correctly
> 
> anything that is able to employ limits and keeps them burstable is
> just perfect :)
> 
> 
> -- 
> the purpose of libvirt is to provide an abstraction layer hiding all
> xen features added since 2006 until they were finally understood and
> copied by the kvm devs.

      reply	other threads:[~2011-06-28 13:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  8:29 VM disk I/O limit patch Andrew Xu
2011-06-21 13:33 ` Konrad Rzeszutek Wilk
2011-06-22 12:06   ` [Xen-users] " Andrew Xu
2011-06-22 13:11     ` Konrad Rzeszutek Wilk
2011-06-22 14:12       ` Re[2]: " Andrew Xu
2011-06-22 14:39         ` Konrad Rzeszutek Wilk
2011-06-24 14:29         ` Re[2]: " Ian Jackson
2011-06-22 12:16   ` Re: [Xen-devel] " Florian Heigl
2011-06-22 13:07     ` [Xen-users] " Konrad Rzeszutek Wilk
2011-06-23 20:45 ` Shaun Reitan
2011-06-27 15:41   ` Konrad Rzeszutek Wilk
2011-06-27 19:22     ` Shaun Reitan
2011-06-28 11:32     ` Re: [Xen-devel] " Florian Heigl
2011-06-28 13:29       ` Konrad Rzeszutek Wilk [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=20110628132957.GC7777@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=florian.heigl@gmail.com \
    --cc=mailinglists@unix-scripts.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-users@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.