From: Markus Klotzbuecher <mk@creamnet.de>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] mini_fo-0.6.0 overlay file system
Date: Fri, 13 May 2005 22:18:15 +0200 [thread overview]
Message-ID: <20050513201814.GA8208@mary> (raw)
In-Reply-To: <2F200E69-465D-46ED-9D3A-5ED5C9FEAC9A@mac.com>
On Thu, May 12, 2005 at 11:18:36PM -0400, Kyle Moffett wrote:
> 2) When forced to copy data, the copy should be done in the context of
> whatever process is doing the "write" operation, and be interruptible,
> etc. The end result is that if you union an nfs mount over another one,
> it will just seem like a write to a big file takes a _really_ long time
> to complete.
This is what happens with mini_fo, provided your kernel is preemptive.
> 3) ext2/3 should get an extra flag for files and directories that
> indicates nonresidence. This would be used by the VFS union layer to
[...]
I like the idea of copying modified data on a per block basis. This
really would avoid unnecessary long copy operations and potentially
save a lot of storage. But I think a unifying layer should not rely on
specialities such as sparse files or flags provided by the lower layer
file systems.
Markus
prev parent reply other threads:[~2005-05-13 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 18:40 [ANNOUNCE] mini_fo-0.6.0 overlay file system Markus Klotzbuecher
2005-05-10 6:07 ` Eric Lammerts
2005-05-10 15:29 ` Lee Revell
2005-05-10 15:42 ` Arjan van de Ven
2005-05-10 17:01 ` Markus Klotzbuecher
2005-05-12 12:18 ` Jörn Engel
2005-05-12 16:44 ` Markus Klotzbuecher
2005-05-13 3:18 ` Kyle Moffett
2005-05-13 8:01 ` Jörn Engel
2005-05-13 11:26 ` Kyle Moffett
2005-05-13 12:24 ` Jörn Engel
2005-05-13 20:57 ` Kyle Moffett
2005-05-13 12:49 ` Jan Blunck
2005-05-13 20:18 ` Markus Klotzbuecher [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=20050513201814.GA8208@mary \
--to=mk@creamnet.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox