From: Jamie Lokier <jamie@shareable.org>
To: "John T. Kohl" <jtk@us.ibm.com>
Cc: Erez Zadok <ezk@cs.sunysb.edu>,
David Howells <dhowells@redhat.com>,
Nikolai Joukov <kolya@cs.sunysb.edu>,
Trond Myklebust <trondmy@trondhjem.org>,
nfsv4@linux-nfs.org, Charles Wright <cwright@cs.sunysb.edu>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] Support for stackable file systems on top of nfs
Date: Mon, 14 Nov 2005 21:32:54 +0000 [thread overview]
Message-ID: <20051114213254.GA29776@mail.shareable.org> (raw)
In-Reply-To: <200511142113.jAELDHfx017507@sumu.lexma.ibm.com>
John T. Kohl wrote:
> >>>>> "Erez" == Erez Zadok <ezk@cs.sunysb.edu> writes:
>
> Erez> Will this work? Will it give us the functionality we need?
> Or would we Erez> need a single page to possibly point back to a
> _chain_ of inodes (which Erez> would start looking like Skinner's
> "pvnode" '93 idea)?
>
> Also have a look at Heidemann's PhD thesis,
> http://www.isi.edu:80/people/johnh/PAPERS/Heidemann95e.html
This looks like it might also have relevance to "copy-on-write" copied
files - multiple inodes, on the same filesystem, sharing pages in
memory as well as on disk. Good for virtual machines sharing files, etc.
A key feature of COW files is the need to mmap() them, and for
modifications to one to not affect the mapped view of the other.
Pages attached to multiple inodes would be a way of implementing that.
I don't have time to write more, so I'm just putting out the
observation.
-- Jamie
next prev parent reply other threads:[~2005-11-14 21:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 0:44 [RFC] Support for stackable file systems on top of nfs Nikolai Joukov
2005-11-14 16:02 ` David Howells
2005-11-14 20:48 ` Erez Zadok
2005-11-14 21:13 ` John T. Kohl
2005-11-14 21:32 ` Jamie Lokier [this message]
2005-11-14 16:11 ` John T. Kohl
-- strict thread matches above, loose matches on Subject: below --
2005-11-10 17:32 Dave Kleikamp
2005-11-10 20:07 ` Christoph Hellwig
2005-11-10 21:35 ` John T. Kohl
2005-11-10 21:40 ` Shaya Potter
2005-11-10 21:57 ` John T. Kohl
2005-11-10 21:50 ` Christoph Hellwig
2005-11-11 2:31 ` Trond Myklebust
2005-11-11 4:04 ` Trond Myklebust
2005-11-11 13:45 ` John T. Kohl
2005-11-11 15:27 ` Charles P. Wright
2005-11-11 17:38 ` John T. Kohl
2005-11-14 15:56 ` David Howells
2005-11-10 21:24 ` Trond Myklebust
2005-11-10 21:36 ` Shaya Potter
2005-11-10 22:18 ` Trond Myklebust
2005-11-10 22:27 ` Shaya Potter
2005-11-10 22:40 ` Trond Myklebust
2005-11-11 0:12 ` Bryan Henderson
2005-11-11 1:30 ` Brad Boyer
2005-11-11 2:06 ` Trond Myklebust
2005-11-11 18:18 ` Bryan Henderson
2005-11-11 19:22 ` Trond Myklebust
2005-11-11 21:57 ` Bryan Henderson
2005-11-11 22:41 ` Trond Myklebust
2005-11-14 19:02 ` Bryan Henderson
2005-11-11 16:40 ` Nikita Danilov
2005-11-11 18:45 ` Bryan Henderson
2005-11-11 19:31 ` Nikita Danilov
2005-11-11 19:42 ` Trond Myklebust
2005-11-11 23:13 ` Bryan Henderson
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=20051114213254.GA29776@mail.shareable.org \
--to=jamie@shareable.org \
--cc=cwright@cs.sunysb.edu \
--cc=dhowells@redhat.com \
--cc=ezk@cs.sunysb.edu \
--cc=jtk@us.ibm.com \
--cc=kolya@cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=trondmy@trondhjem.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;
as well as URLs for NNTP newsgroup(s).