From: Charles Duffy <charles@dyfis.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [BUG] Regression of exec migration
Date: Tue, 01 Sep 2009 15:37:10 -0500 [thread overview]
Message-ID: <h7k0m8$s30$1@ger.gmane.org> (raw)
In-Reply-To: <1035D85E-79C1-4F45-B4E7-90E74260D43C@irisa.fr>
Pierre Riteau wrote:
> I'm afraid this solves the problem only because you disabled non
> blocking operations on the file descriptor, effectively reverting
> 907500095851230a480b14bc852c4e49d32cb16d.
> See comment inline.
Indeed -- fixing this oversight, I'm seeing 2m30s to write an 84mb ramsave.
This doesn't seem to square with Anthony's suggestion that the f*
functions are to blame; we're still doing an fdopen() call and using f*
on incoming migrations, but it's not incoming migrations where we're
having performance issues.
next prev parent reply other threads:[~2009-09-01 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 9:19 [Qemu-devel] [BUG] Regression of exec migration Pierre Riteau
2009-08-27 14:13 ` Anthony Liguori
2009-08-27 16:16 ` Pierre Riteau
2009-08-27 16:24 ` Anthony Liguori
2009-08-28 13:04 ` Pierre Riteau
2009-08-28 15:41 ` Anthony Liguori
2009-08-31 22:55 ` [Qemu-devel] " Charles Duffy
2009-09-01 11:57 ` Pierre Riteau
2009-09-01 20:37 ` Charles Duffy [this message]
[not found] <B2D4B7D8-CF34-4E6D-9772-266E5B1A75C8@irisa.fr>
2009-08-27 13:31 ` Chris Lalancette
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='h7k0m8$s30$1@ger.gmane.org' \
--to=charles@dyfis.net \
--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 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.