The vfs-scale branch is now upstream. If you haven't looked yet, your filesystem is likely to have been touched, so check it out. Also look at Documentation/filesystems/porting and path-lookup.txt. The dcache_lock stuff should have been all done for you (for in-tree filesystems, I can help out of tree fses with conversions there if you ping me offline). The rcu-walk stuff can be more tricky for your filesystem to take advantage of. If you supply a .d_revalidate, .permission, or .check_acl, then path walking is going to be slow and unscalable for you. Out of tree filesystems: you _have_ to at least add a line of code to the above functions in order to specify that you don't want to participate in rcu-walk. Otherwise, you don't have to care about rcu-walk if you have a legacy or special filesystem like configfs then I'd advise against anything fancy. But if you have a userbase and you expect them to actually do any path lookups into your filesystem, please take a look. This is a big and complex change by any measure, so please don't be afraid to ask for help or clarification. I'd also really like to be able to update documentation based on questions from fs maintainers (in and out of tree) who are trying to follow it and bring their code up to speed. Thanks, Nick -- 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
