From: Thomas Treutner <thomas@scripty.at>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Migration speed throttling, max_throttle in migration.c
Date: Wed, 09 Feb 2011 22:18:02 +0100 [thread overview]
Message-ID: <4D53048A.8090208@scripty.at> (raw)
In-Reply-To: <4D52F2DE.8070103@codemonkey.ws>
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?
regards,
thomas
next prev parent reply other threads:[~2011-02-09 21:18 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 [this message]
2011-02-10 5:52 ` Yoshiaki Tamura
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=4D53048A.8090208@scripty.at \
--to=thomas@scripty.at \
--cc=anthony@codemonkey.ws \
--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).