qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Lyu Mitnick <mitnick.lyu@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] GSoC: Improved image format compatibility
Date: Sat, 2 Apr 2011 02:29:40 +0800	[thread overview]
Message-ID: <AANLkTim2WJ_EvatL+cq-4QiYUj2ybMH_eatsT_-pm-iH@mail.gmail.com> (raw)
In-Reply-To: <4D95FD80.6050303@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

Hello

I have some question about asynchronous i/o in QEMU block driver: Why a file
format with asynchronous i/o support(ex. qcow) doesn't need to register
bdrv_read/bdrv_write which is registered in vhd file format?? Would qcow
block driver
also support synchronous i/o??

thanks a lot

Mitnick

2011/4/2 Kevin Wolf <kwolf@redhat.com>

> Am 01.04.2011 17:15, schrieb Lyu Mitnick:
> > Hello Stefan
> >
> >     Hello Mitnick,
> >
> >     asynchronous i/o is also missing in block/vpc.c.
> >
> >     All newer block drivers support asynchronous reads and writes,
> >     only some old drivers don't.
> >
> >     So adding asynchronous i/o to at least some of the old drivers
> >     would improve their usability.
> >
> >     Look for "aio" in block/*.c to get a starting point.
> >
> >     Regards
> >     Stefan (W.)
> >
> >
> > I look for "aio" in block/*.c as a starting point of asynchronous i/o.
> > And I
> > found that there isn't any "aio" keywords in block/vmdk.c. block/vmdk.c
> > is used as block driver for the VMDK format. Is it means that
> asynchronous
> > i/o is also missing in VMDK format?
>
> Yes, the VMDK implementation is completely synchronous.
>
> Kevin
>

[-- Attachment #2: Type: text/html, Size: 1808 bytes --]

  reply	other threads:[~2011-04-01 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 21:55 [Qemu-devel] GSoC: Improved image format compatibility Lyu Mitnick
2011-03-30  4:50 ` Stefan Weil
2011-03-30  8:32   ` Stefan Hajnoczi
2011-03-30 18:40     ` Lyu Mitnick
2011-03-30 19:11       ` Stefan Weil
2011-03-30 19:36         ` Lyu Mitnick
2011-04-01 15:15         ` Lyu Mitnick
2011-04-01 16:29           ` Kevin Wolf
2011-04-01 18:29             ` Lyu Mitnick [this message]
2011-04-02 13:54               ` Stefan Hajnoczi
2011-04-02 19:03                 ` Lyu Mitnick
2011-04-03  7:33                   ` Stefan Hajnoczi
2011-04-04 17:35                     ` Lyu Mitnick
2011-04-01 17:02           ` Stefan Weil

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=AANLkTim2WJ_EvatL+cq-4QiYUj2ybMH_eatsT_-pm-iH@mail.gmail.com \
    --to=mitnick.lyu@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 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).