From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
"Erik Rull" <erik.rull@rdsoftware.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Stefan Hajnoczi" <stefanha@gmail.com>
Subject: Re: [Qemu-devel] Boot Problems Windows XP guest
Date: Wed, 28 Aug 2013 16:05:24 +0200 [thread overview]
Message-ID: <20130828140524.GD6170@irqsave.net> (raw)
In-Reply-To: <521E0247.7060202@redhat.com>
> Yes, I'm afraid that the burst is problematic here since the current
> throttling algorithm doesn't help (and IIUC it behaves as if it had
> max=avg/10 due to the 100ms slice time). This is Windows so no CFQ
> here. Do you need to set bps_max=1 or will bps_max=0 work too?
In it's current state the code will overwrite the burst if it's set smaller than
avg/10.
The result will be a small initial spike of size avg/10 then it will cap to avg.
Best regards
Benoît
next prev parent reply other threads:[~2013-08-28 14:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 9:52 [Qemu-devel] Boot Problems Windows XP guest Erik Rull
2013-08-27 7:38 ` Stefan Hajnoczi
2013-08-27 20:26 ` Erik Rull
2013-08-27 21:31 ` Paolo Bonzini
2013-08-27 21:37 ` Anthony Liguori
2013-08-28 8:05 ` Erik Rull
2013-08-28 11:05 ` Paolo Bonzini
2013-08-28 7:50 ` Stefan Hajnoczi
2013-08-28 9:07 ` Erik Rull
2013-08-28 13:14 ` Paolo Bonzini
2013-08-28 13:34 ` Benoît Canet
2013-08-28 13:41 ` Paolo Bonzini
2013-08-28 13:51 ` Benoît Canet
2013-08-28 13:59 ` Paolo Bonzini
2013-08-28 14:05 ` Benoît Canet [this message]
2013-08-28 14:05 ` Paolo Bonzini
2013-08-28 14:26 ` Benoît Canet
2013-08-28 18:21 ` Erik Rull
2013-08-28 18:40 ` Benoît Canet
2013-08-28 19:22 ` Erik Rull
2013-08-29 7:53 ` Erik Rull
2013-08-29 9:25 ` Benoît Canet
2013-08-29 14:51 ` Erik Rull
2013-08-29 14:55 ` Paolo Bonzini
2013-08-29 15:31 ` Erik Rull
2013-08-28 13:19 ` 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=20130828140524.GD6170@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=erik.rull@rdsoftware.de \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.