All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: Ion Badulescu <ionut@badula.org>
Cc: "Charles P. Wright" <cpwright@cpwright.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-fsdevel@vger.kernel.org, ezk@cs.sunysb.edu
Subject: Re: Sick VFS question
Date: Fri, 07 Mar 2003 00:53:53 +0800	[thread overview]
Message-ID: <3E677D21.9050208@shaolinmicro.com> (raw)
In-Reply-To: Pine.LNX.4.44.0302251334430.32233-100000@guppy.limebrokerage.com

Ion Badulescu wrote:

>On Tue, 25 Feb 2003, Charles P. Wright wrote:
>
>  
>
>>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.
>>    
>>
>
>Hmm. You're probably right (you've been hacking that code more recently
>than I have...). Anyway, what I said initially was definitely the original
>approach for FiST-lite, and I guess my memory is getting fuzzy on recent
>details, even though I actively worked on them. :-)
>  
>
 From what I know about FiST, this is not quite true. The aops of wrapfs 
inode are not pointed to the lower level fs's aops. Most of the address 
space operations have a struct page, which a struct page have its 
mapping and host ref to inode. The lower level inode is ref by the 
wrapfs inode private data. The wrapgs has its own page cache and looks 
like a separate fs to the VFS in all aspects.

David


  parent reply	other threads:[~2003-03-06 16:53 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
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 [this message]
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=3E677D21.9050208@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=cpwright@cpwright.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=hpa@zytor.com \
    --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 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.