All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>, Chunqiang Tang <ctang@us.ibm.com>,
	Eric Van Hensbergen <ericvh@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Moving beyond image files
Date: Mon, 21 Mar 2011 11:04:31 -0500	[thread overview]
Message-ID: <4D87770F.3080407@codemonkey.ws> (raw)
In-Reply-To: <145C4163-3365-4A73-B2F2-EC397669D363@suse.de>

On 03/21/2011 10:16 AM, Alexander Graf wrote:
> On 21.03.2011, at 16:05, Anthony Liguori wrote:
>
>>
>> 5) Copy-on-write references potentially become very interesting for image streaming because you can avoid any I/O for blocks that are already stored locally.
>>
>> This is not fully baked yet but I thought I'd at least throw it out there as a topic for discussion.  I think we've focused almost entirely on single images so I think it's worth thinking a little about different storage models.
> Wouldn't it make sense to have your file system be that daemon

I see that as purely an implementation detail.

Regards,

Anthony Liguori

>   and add an interface to it so you can receive the sha1 sums (that you need for dedup anyways) to calculate rsync style diffs?
>
> That way you'd also speed up 2 other use cases:
>
>    a) normal raw storage - no need to implement new protocols, file formats, etc
>    b) real rsync on real data that is not vm images
>
>
> Alex
>
>

  reply	other threads:[~2011-03-21 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 15:05 [Qemu-devel] Moving beyond image files Anthony Liguori
2011-03-21 15:16 ` Alexander Graf
2011-03-21 16:04   ` Anthony Liguori [this message]
2011-03-21 21:35 ` 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=4D87770F.3080407@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=agraf@suse.de \
    --cc=ctang@us.ibm.com \
    --cc=ericvh@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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.