From: =?gb18030?B?usa3rrCh?= <fanh2010@foxmail.com>
To: =?gb18030?B?cWVtdS1kZXZlbA==?= <qemu-devel@nongnu.org>
Subject: [Qemu-devel] some confusion on qemu i/o pocess and the qcow2 format
Date: Fri, 20 Nov 2015 11:21:14 +0800 [thread overview]
Message-ID: <tencent_392D68C105B01F83050CF831@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 207 bytes --]
1.what is the difference of bdrv_co_readv and bdrv_aio_readv£¿
2.I am confused about the I/O pocess of qcow2, i find. Can anybody tell me the detail pocess? or arethere any useful tools to trace the pocess?
[-- Attachment #2: Type: text/html, Size: 232 bytes --]
next reply other threads:[~2015-11-20 3:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 3:21 =?gb18030?B?usa3rrCh?= [this message]
2015-11-25 9:44 ` [Qemu-devel] some confusion on qemu i/o pocess and the qcow2 format Stefan Hajnoczi
[not found] ` <tencent_04C6AF085D5F3396311ECC83@qq.com>
2015-12-02 13:29 ` [Qemu-devel] 回复： some confusion on qemu i/o pocess and the qcow2format Stefan Hajnoczi
2015-12-21 2:48 ` [Qemu-devel] =?gb18030?b?u9i4tKO6ICC72Li0o7ogIHNvbWVjb25mdXNpb24g?= =?gb18030?q?on_qemu_i/o_pocess_and_the_qcow2format?= =?gb18030?B?usa3rrCh?=
2015-12-22 6:35 ` [Qemu-devel] 回复： 回复： someconfusion on qemu i/o pocess and the qcow2format 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=tencent_392D68C105B01F83050CF831@qq.com \
--to=fanh2010@foxmail.com \
--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).