Skip to contentSkip to conversation

Overhead of Using a Stackable File System(Wrapfs)

DISCUSSION UZAIR LAKHANI 3 participants 6 messages Apr 2, 2006 – Apr 9, 2006 VFS

lore
Share & tools
lore
#0 lore raw

Hello All,

I want to enquire about the percent overhead involved when we use Wrapfs(null layer stacking file system) over ext3.

I want to enquire this because I want to use Wrapfs in a network environment and there will be an additional overhead of network communication.

Thanks,
Uzair Lakhani,
Karachi, Pakistan.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#1 lore raw
Quoted 5 lines · UZAIR LAKHANI

Hello All,

I want to enquire about the percent overhead involved when we use Wrapfs(null layer stacking file system) over ext3.

It should only be a few percent (if I remember correctly, less than 5), but it would depend on your machine and workload. If you want an exact answer, just run some benchmarks on ext3 and wrapfs/ext3.

Quoted 3 lines

I want to enquire this because I want to use Wrapfs in a network environment and there will be an additional overhead of network communication.

If you're still talking about implementing NFS using stackable file systems, please note that we decided that was not a good idea.

Good luck.

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

#2 lore raw
Quoted 19 lines · --- Avishay Traeger
Quoted 3 lines · UZAIR LAKHANI

Hello All,

I want to enquire about the percent overhead

involved

Quoted 1 line

when we use Wrapfs(null layer stacking file

system)

Quoted 1 line

over ext3.

It should only be a few percent (if I remember
correctly, less than 5),
but it would depend on your machine and workload.
If you want an exact
answer, just run some benchmarks on ext3 and
wrapfs/ext3.

Quoted 1 line

I want to enquire this because I want to use

Wrapfs in

Quoted 8 lines
Quoted 1 line

a network environment and there will be an

additional

Quoted 1 line

overhead of network communication.

If you're still talking about implementing NFS using stackable file
systems, please note that we decided that was not a good idea.

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.

Quoted 7 lines

Good luck.

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

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

#3 lore raw
Quoted 9 lines · UZAIR LAKHANI

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

Quoted 8 lines

(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/

#4 lore raw
Quoted 25 lines · --- Avishay Traeger
Quoted 5 lines · UZAIR LAKHANI

Thanks for replying but consider this scenario.

What Wrapfs code do is this

user_request ---> vfs_request ---> wrapfs_request

--->

Quoted 3 lines

actual_fs_request ---> storage

Now consider this scenario in a network

environment

Quoted 3 lines

(client machine)
user_request ---> vfs_request ---> wrapfs_request

--->

Quoted 2 lines

Network ---> (server machine)actual_fs_request

--->

Quoted 3 lines

storage

The network here gets client requests and send

them to

Quoted 1 line

server and vice versa.

Quoted 17 lines

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.

Thanks again for replying. I am getting your point that we don't have any lower filesystem on the client side but can we not assume that we have a lower file sytem on client side but that actually resides across the network on server side. All then we have to do is to pass the requsts for the lower file system on client side to the lower file system on server side using some communication mechanism.

Waiting for comments.

Thanks,
Uzair

Quoted 4 lines

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

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com