From: "H. Peter Anvin" <hpa@zytor.com>
To: "Charles P. Wright" <cpwright@cpwright.com>
Cc: Ion Badulescu <ionut@badula.org>,
linux-fsdevel@vger.kernel.org, ezk@cs.sunysb.edu
Subject: Re: Sick VFS question
Date: Tue, 25 Feb 2003 09:57:30 -0800 [thread overview]
Message-ID: <3E5BAE8A.7030607@zytor.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302251224420.32495-100000@cpwright.com
Charles P. Wright wrote:
>
> I don't believe this is the case.
>
> I think what was suggested is EXT2 dentry (or other "real" fs) points to
> an autofs inode. I'm not sure if this would work or not, but I don't
> think it is the same as FiST-lite.
>
That is, indeed, what I'm trying to accomplish.
> AFAIK, In FiST-lite what happens is the upper level (wrapfs) inode has its
> address space operations set to the operations of the lower level (e.g.,
> EXT2) inode. A quick look at the code seemed to confirm this.
>
> The EXT2 dentry still points to the inode of ext2, and the wrapfs dentry
> still points to a wrapfs inode. The change is wrapfs inode's
> i_mapping->a_ops points to the EXT2 inode's i_mapping->a_ops.
This sounds like it takes a file and "maps" it on top of another file --
something that would probably make a viable implementation of cachefs if
we'd ever get around to implementing that...
-hpa
next prev parent reply other threads:[~2003-02-25 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 9:48 Sick VFS question H. Peter Anvin
2003-02-25 16:19 ` Ion Badulescu
2003-02-25 17:30 ` Charles P. Wright
2003-02-25 17:57 ` H. Peter Anvin [this message]
2003-02-25 18:46 ` Ion Badulescu
2003-02-25 19:53 ` H. Peter Anvin
2003-02-25 20:39 ` Ion Badulescu
2003-02-25 21:06 ` Ion Badulescu
2003-02-25 21:55 ` H. Peter Anvin
2003-02-26 15:37 ` Erez Zadok
2003-02-26 15:45 ` H. Peter Anvin
2003-03-06 16:53 ` David Chow
2003-03-06 17:18 ` Charles P. Wright
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=3E5BAE8A.7030607@zytor.com \
--to=hpa@zytor.com \
--cc=cpwright@cpwright.com \
--cc=ezk@cs.sunysb.edu \
--cc=ionut@badula.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).