From: Vladimir Saveliev <vs@namesys.com>
To: Roland Paterson-Jones <roland@rolandpj.com>
Cc: reiserfs-list@namesys.com
Subject: Re: File-level copy-on-write?
Date: Fri, 11 Feb 2005 14:42:58 +0300 [thread overview]
Message-ID: <1108122178.3899.95.camel@tribesman.namesys.com> (raw)
In-Reply-To: <420C6A4F.2060905@rolandpj.com>
Hello
On Fri, 2005-02-11 at 11:18, Roland Paterson-Jones wrote:
> Hi
>
> I have an application where I want to make relatively frequent copies of
> a large file, and the copies will remain largely similar to the original.
>
> It seems to me that a file-level copy-on-write would support this well.
>
> So, does reiserfs support anything like this?
>
No.
> If not, can I implement this easily (how easily ;) ) with a plugin.
>
I guess you mean plugin for reiser4?
You probably can but I do not think that it would be easy.
> Any ideas and pointers greatfully received
I think it would be easier to modify the application.
You should probably start with detailed definition of your COW protocol.
> Thanks
> Roland
>
>
next prev parent reply other threads:[~2005-02-11 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 8:18 File-level copy-on-write? Roland Paterson-Jones
2005-02-11 11:42 ` Vladimir Saveliev [this message]
2005-02-12 5:14 ` David Masover
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=1108122178.3899.95.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=roland@rolandpj.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.