From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Thomas Treutner <thomas@scripty.at>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Migration speed throttling, max_throttle in migration.c
Date: Thu, 10 Feb 2011 14:52:24 +0900 [thread overview]
Message-ID: <AANLkTi=oPnGuSkmddGt-DrZ_3S1iBiRhOFx72Neomf6a@mail.gmail.com> (raw)
In-Reply-To: <4D53048A.8090208@scripty.at>
2011/2/10 Thomas Treutner <thomas@scripty.at>:
> Am 09.02.2011 21:02, schrieb Anthony Liguori:
>>
>> The reason it's still this today is mainly historic. I've thought about
>> making the default limit unlimited. I'm not sure if anyone has strong
>> opinions.
>
> Personally, I'd appreciate that. TCP's congestion control when using 100MBit
> Ethernet seems to work fine (as there are no complaints?) so I see no reason
> why the bandwidth shouldn't be unlimited in general and TCP should adapt to
> the available bandwidth. If one wants to limit bandwidth manually, that's
> possible of course.
>
> I don't know if such a change would affect all other existing ways of saving
> a VM, with different consequences?
I would prefer to have live migration speed unlimited, but there
might be cases that the response speed of qemu monitor gets bad
in low spec environments? Especially if you use block migration,
the overhead should be far more than usual live migration.
Thanks,
Yoshi
>
>
> regards,
> thomas
>
>
prev parent reply other threads:[~2011-02-10 5:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 18:13 [Qemu-devel] Migration speed throttling, max_throttle in migration.c Thomas Treutner
2011-02-09 20:02 ` Anthony Liguori
2011-02-09 21:18 ` Thomas Treutner
2011-02-10 5:52 ` Yoshiaki Tamura [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='AANLkTi=oPnGuSkmddGt-DrZ_3S1iBiRhOFx72Neomf6a@mail.gmail.com' \
--to=tamura.yoshiaki@lab.ntt.co.jp \
--cc=qemu-devel@nongnu.org \
--cc=thomas@scripty.at \
/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).