From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Lieven <pl@dlhnet.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] livelock in iolimits
Date: Thu, 10 Jan 2013 13:45:39 +0100 [thread overview]
Message-ID: <20130110124539.GG30946@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <FB71912E-FA31-4C49-ADA9-AB87A6020AE7@dlhnet.de>
On Tue, Jan 08, 2013 at 04:43:22PM +0100, Peter Lieven wrote:
> i am experimenting with iolimits on a virtio block device and found a lock condition.
> My plan was to monitor IOPS and/or bandwidth and kick a limit in if a vServer is exhausting
> these limits too much.
> However, it seems that if a limit is defined while the defined limit is exceeded no further I/O
> is processed.
You have sent a fix for this?
Just double-checking that this email thread can be ignored in favor of
your patch.
Stefan
next prev parent reply other threads:[~2013-01-10 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 15:43 [Qemu-devel] livelock in iolimits Peter Lieven
2013-01-10 12:45 ` Stefan Hajnoczi [this message]
2013-01-10 12:48 ` Peter Lieven
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=20130110124539.GG30946@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=pl@dlhnet.de \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).