All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Zhi Yong Wu <wuzhy@cn.ibm.com>
Subject: Re: [Qemu-devel] [RFC 0/4] block: fix I/O throttling oscillations
Date: Thu, 21 Mar 2013 16:27:29 +0100	[thread overview]
Message-ID: <20130321152729.GF4259@irqsave.net> (raw)
In-Reply-To: <1363877399-16339-1-git-send-email-stefanha@redhat.com>

> I have also included two code clean-up patches.
> 
> Benoît: Please let me know if this solves the problems you're seeing.

Hello Stefan,

It seems super stable on my test setup.
I will deploy the patchset on the production setup to see if it solves
the problem that the user is seeing.
I should know if it work by the end of the next week.
If it works this patchset will have a super strong Tested-By:

Best regards

Benoît

  parent reply	other threads:[~2013-03-21 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 14:49 [Qemu-devel] [RFC 0/4] block: fix I/O throttling oscillations Stefan Hajnoczi
2013-03-21 14:49 ` [Qemu-devel] [RFC 1/4] block: fix I/O throttling accounting blind spot Stefan Hajnoczi
2013-03-27  8:50   ` Zhi Yong Wu
2013-03-27  9:14     ` Stefan Hajnoczi
2013-03-27 12:49       ` Zhi Yong Wu
2013-03-21 14:49 ` [Qemu-devel] [RFC 2/4] block: keep I/O throttling slice time constant Stefan Hajnoczi
2013-03-21 14:49 ` [Qemu-devel] [RFC 3/4] block: drop duplicated slice extension code Stefan Hajnoczi
2013-03-21 14:49 ` [Qemu-devel] [RFC 4/4] block: clean up I/O throttling wait_time code Stefan Hajnoczi
2013-03-21 15:27 ` Benoît Canet [this message]
2013-03-21 16:34   ` [Qemu-devel] [RFC 0/4] block: fix I/O throttling oscillations Stefan Hajnoczi
2013-03-27 12:55 ` Zhi Yong Wu
2013-04-04 12:15 ` Benoît Canet
2013-04-04 16:24   ` Kevin Wolf
2013-04-04 16:30     ` Stefan Hajnoczi

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=20130321152729.GF4259@irqsave.net \
    --to=benoit.canet@irqsave.net \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wuzhy@cn.ibm.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.