Messages in this thread | | | Date | Fri, 3 Sep 2004 00:59:42 +0530 | From | Amit Gud <> | Subject | Using filesystem blocks |
| |
I don't know if this has been already discussed on the list before.
Is it wise enough to abstract away the usage of blocks for storing extended attributes? I mean can the code - of using filesystem blocks, putting headers and all data in place within the blocks, managing the block boundaries, padding ... - be taken away from within the xattr code. I know xattr is filesystem specific, but if most of filesystems are using blocks not associated with any inode to store xattr-specifc information it could well be taken to a different layer - just like mbcache. Almost only ext2/3 uses mbcache - and that too only for xattr - but it is implemented at an abstract level.
Not only this would add to the modularization, this can help other filesystems if they want to use filesystem blocks. Like if one wishes to implement distributed filesystem, he may prefer to store the FS metadata in blocks rather than in files. Is it advisible for him to redo the code, which is very beautifully written in ext2/3 ? I think not.
AG - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |