|
Size: 331
Comment:
|
Size: 896
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. More info will come soon... | This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution. |
| Line 5: | Line 5: |
| This is still INCOMPLETE!!! | == Why choose this stuff == * The filesystem has to be mounted after the roots are mounted when using the standard module. With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly * You get caching which speeds things up a lot for free * You get nice stats (optional) == Why NOT choose it == * Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner |
| Line 12: | Line 20: |
| == TODO == * Add support for creating directories * Add support for choice which roots are read-only and which are not * Add cache controls |
unionfs-fuse
This is my effort to create a unionfs implementation which is probably slower but way more flexible than the current in-kernel unionfs solution.
Why choose this stuff
- The filesystem has to be mounted after the roots are mounted when using the standard module. With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly
- You get caching which speeds things up a lot for free
- You get nice stats (optional)
Why NOT choose it
- Compared to kernel-space solution we need lots of useless context switches which makes kernel-only solution clear speed-winner
Available parameters
--roots=/root1,/root2
--stats
TODO
- Add support for creating directories
- Add support for choice which roots are read-only and which are not
- Add cache controls
attachment:unionfs.c