All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Shaun Reitan <mailinglists@unix-scripts.com>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Re: VM disk I/O limit patch
Date: Mon, 27 Jun 2011 11:41:48 -0400	[thread overview]
Message-ID: <20110627154148.GK6978@dumpdata.com> (raw)
In-Reply-To: <iu08lj$l0u$1@dough.gmane.org>

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
> you specified that a guest's bucket could hold say 4000 tokens, and
> the bucket would be filled with 10 tokens a second.  Each IO took
> one token from the bucket.  When the bucket was empty IO was paused
> and processed as the bucket was filled.  This allowed a guest to
> burst for a short period of time until that bucket was empty and
> then it would slowely be filled back up.

Uhhh... are you sure you are talking about the same patch.
> 
> Also what was nice is that the guest had a /proc/ entry that told
> the customer how many tokens they currently had in their bucket.

OK.. but how would this help the customers? They don't have access
to the /proc in Dom0.
> 
> I would like to see somthing like this in Xen, I've even thought
> about posting to the devel forums seeing if somebody wanted to write
> one for $$$

Why not use dm-ioband (here is a doc about it:
http://lwn.net/Articles/344441/) which has much more options and also
provide the bucket and tokens you are looking for.

[edit: Looks like dm-ioband never made it in the Linux kernel. But there
was something that I thought Vivek wrote that was superior to dm-ioband..
Ah, yes: blkio-controller.txt.

Look in Documentation/cgroups/blkio-controller.txt]

  reply	other threads:[~2011-06-27 15:41 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 [this message]
2011-06-27 19:22     ` Shaun Reitan
2011-06-28 11:32     ` Re: [Xen-devel] " Florian Heigl
2011-06-28 13:29       ` [Xen-users] " Konrad Rzeszutek Wilk

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=20110627154148.GK6978@dumpdata.com \
    --to=konrad.wilk@oracle.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.