Re: Overhead of Using a Stackable File System(Wrapfs)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2006-04-07 at 23:48 -0700, UZAIR LAKHANI wrote:
> Thanks for replying but consider this scenario.
> 
> What Wrapfs code do is this 
> 
> user_request ---> vfs_request ---> wrapfs_request --->
> actual_fs_request ---> storage
> 
> Now consider this scenario in a network environment
> 
> (client machine)
> user_request ---> vfs_request ---> wrapfs_request --->
> 
> Network ---> (server machine)actual_fs_request --->
> storage
> 
> The network here gets client requests and send them to
> server and vice versa.

The main benefit of stackable file systems is that you do not need to
duplicate the functionality found in lower-level file systems.  In your
scenario, you do not use the lower-level file system at all, so you will
need to implement all the functionality of a lower-level file system,
plus deal with all the stackable file system code (which you will use
but won't need).  Using wrapfs in this case will give you no benefit,
and will just make your life more difficult, and your code slower and
more difficult to read.  I recommend you just start from scratch.

Avishay Traeger
http://www.fsl.cs.sunysb.edu/~avishay/

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux