Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ray Van Dolson <rayvd@bludgeon.org>, linux-btrfs@vger.kernel.org
Subject: Re: Data-deduplication?
Date: Wed, 15 Oct 2008 19:49:44 +0200	[thread overview]
Message-ID: <48F62D38.5060109@redhat.com> (raw)
In-Reply-To: <20081015141543.GT12131@one.firstfloor.org>

Andi Kleen wrote:

   

>>> There are some patches to do in QEMU's cow format for KVM. That's
>>> user level only.
>>>  
>>>       
>> And thus, doesn't work for sharing between different images, especially 
>> at runtime. 
>>     
>
> It would work if the images are all based once on a reference image, won't it?
>   

Yes and no.  It's difficult to do it at runtime, and it allows one qemu 
to access another guest's data (for read-only).

Also, it's almost impossible to do at runtime.


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-10-15 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12  2:06 Data-deduplication? Ray Van Dolson
2008-10-13  8:52 ` Data-deduplication? Andi Kleen
2008-10-15 13:39   ` Data-deduplication? Avi Kivity
2008-10-15 14:15     ` Data-deduplication? Andi Kleen
2008-10-15 14:43       ` Data-deduplication? Miguel Sousa Filipe
2008-10-15 15:00         ` Data-deduplication? Andi Kleen
2008-10-15 17:49       ` Avi Kivity [this message]
2008-10-13 11:02 ` Data-deduplication? Chris Mason
2008-10-16 19:25   ` Data-deduplication? Valerie Aurora Henson
2008-10-16 19:30     ` Data-deduplication? Chris Mason
2008-10-17 18:24       ` Data-deduplication? Valerie Aurora Henson
2008-10-20  0:16         ` Data-deduplication? Chris Mason
2008-10-21 20:33           ` Data-deduplication? Valerie Aurora Henson
2008-10-17 20:10     ` Data-deduplication? Christoph Hellwig

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=48F62D38.5060109@redhat.com \
    --to=avi@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rayvd@bludgeon.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