From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Uri Lublin <uril@redhat.com>
Subject: Re: [Qemu-devel] migration: adding migration to/from a file (v2)
Date: Thu, 19 Feb 2009 14:06:41 -0600 [thread overview]
Message-ID: <499DBBD1.1020602@codemonkey.ws> (raw)
In-Reply-To: <20090219193733.GB22319@shareable.org>
Jamie Lokier wrote:
>
>> Remember, migration is a streaming
>> protocol, not a random access, so it only makes sense to have one
>> outstanding request at a time.
>>
>
> Fwow, often with streaming (in general) the highest performance comes
> from having two or more outstanding requests at a time, so there are
> no gaps between requests being processed at the OS and device level.
>
> However, unless migrate-to-file uses O_DIRECT that will be hidden by
> the OS's buffering.
>
It's already buffered FWIW by the savevm infrastructure. You'll won't
usually see small operations.
Regards,
Anthony Liguori
> Then the remaining overhead from AIOs (or fake AIOs using threads) is
> lots context switching, one per write completed.
>
> -- Jamie
>
>
>
next prev parent reply other threads:[~2009-02-19 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 11:45 [Qemu-devel] migration: adding migration to/from a file (v2) Uri Lublin
2009-02-19 13:57 ` Anthony Liguori
2009-02-19 16:14 ` Uri Lublin
2009-02-19 16:51 ` Anthony Liguori
2009-02-19 19:06 ` Uri Lublin
2009-02-19 20:05 ` Anthony Liguori
2009-02-19 20:28 ` Jamie Lokier
2009-02-19 23:36 ` M. Warner Losh
2009-02-19 23:59 ` Anthony Liguori
2009-02-20 0:36 ` M. Warner Losh
2009-02-19 20:45 ` Uri Lublin
2009-02-19 19:37 ` Jamie Lokier
2009-02-19 20:06 ` Anthony Liguori [this message]
2009-02-19 19:33 ` Jamie Lokier
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=499DBBD1.1020602@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=uril@redhat.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.