On Wed, 18 Sep 2013 11:36:54 +0400, Vyacheslav Dubeyko wrote: > By the way, I am implementing extended attributes (xattr) support in > NILFS2 right now. Sounds great. Could you share your implementation idea again before finishing your patchset? Is the basic idea same as the following RFC? [1] http://www.mail-archive.com/linux-nilfs@xxxxxxxxxxxxxxx/msg01298.html There are several implementation approaches: (1) Add one or multiple xattr meta data files to store xattr blocks. (2) Add xattr btree to each disk inode (this seems to need inode size extension). (3) Use part of inodes to hold xattr data. (4) Extend btree to make holding mutiple data streams possible. And we should first evaluate pros and cons of them to minimize rework, for example, impact on disk format, impact on GC, impact on log writer, and so forth. We also have to decide whether we impose limitation on xattr block size, that is, whether we support mutiple xattr blocks per inode or only support single xattr block per inode. The latter restricted implementation often becomes an issue nowadays. Regards, Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
