From: Christoph Hellwig <hch@lst.de>
To: Lyu Mitnick <mitnick.lyu@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Christoph Hellwig <hch@lst.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] GSoC - QCOW2 <-> QED image converter
Date: Mon, 11 Apr 2011 20:11:00 +0200 [thread overview]
Message-ID: <20110411181100.GA8877@lst.de> (raw)
In-Reply-To: <BANLkTinrOUmcXJf3PjCH8Yt1sQb5X3QwYg@mail.gmail.com>
On Thu, Apr 07, 2011 at 07:10:00AM +0800, Lyu Mitnick wrote:
> Would you mind to share your solution about this feature?? My idea is
> replace
> all bdrv_pread(), bdrv_pwrite_sync(), bdrv_pwrite() in block/vpc.c to
> bdrv_pread_split(), bdrv_pwrite_sync_split(), bdrv_pwrite_split()
> corresponding.
> bdrv_pread_split(), bdrv_pwrite_sync_split(), bdrv_pwrite_split() should
> deal with
> data splitted at different files via bdrv_pread(), bdrv_pwrite_sync(),
> bdrv_pwrite(),
> give an interface of sequential byte accessed. Is it suitable to solve this
> issue??
For the synchronous bdrv_read/bdrv_write used in vmdk the problem actually
is rather trivial, as it already split it's reads/write on a cluster
boundary internally, and the higher level split is always alignment to
a cluster boundary. So basically no new work there.
prev parent reply other threads:[~2011-04-12 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 18:56 [Qemu-devel] GSoC - QCOW2 <-> QED image converter Lyu Mitnick
2011-04-05 9:15 ` Stefan Hajnoczi
2011-04-05 18:03 ` Lyu Mitnick
2011-04-06 6:41 ` Stefan Hajnoczi
2011-04-06 11:13 ` Lyu Mitnick
2011-04-06 12:46 ` Stefan Hajnoczi
2011-04-06 15:06 ` Christoph Hellwig
2011-04-06 15:15 ` Kevin Wolf
2011-04-06 15:52 ` Christoph Hellwig
2011-04-06 23:10 ` Lyu Mitnick
2011-04-11 18:11 ` Christoph Hellwig [this message]
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=20110411181100.GA8877@lst.de \
--to=hch@lst.de \
--cc=kwolf@redhat.com \
--cc=mitnick.lyu@gmail.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 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.