From: Gordan Bobic <gordan@bobich.net>
To: David Nicol <davidnicol@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
BTRFS MAILING LIST <linux-btrfs@vger.kernel.org>
Subject: Re: VFS support for fast copy on deduplicating FSes
Date: Thu, 25 Nov 2010 10:36:11 +0000 [thread overview]
Message-ID: <4CEE3C1B.9030009@bobich.net> (raw)
In-Reply-To: <AANLkTinz17SePZCCixBCA_WoW3rFWAsB7mRghL9uN17h@mail.gmail.com>
David Nicol wrote:
> unresearched question/suggestion:
>
> Is there general support for a "fast copy" ioctl in the VFS layer,
> which would be hooked by file systems that support COW or other forms
> of deduplication and can provide copy semantics by manipulating
> metadata only?
What would be nice to have is something that provides functionality like
this:
http://www.xmailserver.org/flcow.html
My use case is to do with chroot-type virtualization, to save DLL memory
and disk space, but the author's use case is clearly different.
Vserver does something similar transparently within the combined
guest-spaces (i.e. once you hashify the files, you no longer have 10
instances of the identical glibc for 10 guests, and they are no longer
using 10x the RAM and disk space), and when the file is touched for
writing it COWs a new copy.
It would be nice to have something like this exist on FS level without
need for patching by the likes of vserver, by simply applying a flag to
files we want to be COW-ed (chattr?).
Having this work across snapshots is potentially a bit dubious. I can
see why it might be a bad idea, so perhaps a better way might be to have
something that works semantically and syntactically similar to snapshots
for duplicating directory subtrees into COW copies?
Gordan
prev parent reply other threads:[~2010-11-25 10:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 10:19 VFS support for fast copy on deduplicating FSes David Nicol
2010-11-25 10:32 ` Tomasz Torcz
2010-11-25 10:50 ` Pádraig Brady
2010-11-25 10:36 ` Gordan Bobic [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=4CEE3C1B.9030009@bobich.net \
--to=gordan@bobich.net \
--cc=davidnicol@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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