On Mon, May 14, 2012 at 11:27:42AM -0600, Andreas Dilger wrote: > > And if it at all possible I'd rather have it be something that Just > > Works rather than something that requires extra configuration. > > Sure, but this is only useful for NFSv4, but costs everyone using > ext4 continuous overhead, so it isn't a clear-cut case to enable > the version just on the thought that NFS might one day be used on > any particular filesystem. It's not a matter of "NFSv4 might one day be used"; if we don't turn on i_version updates until the file system is actually exported via NFSv4, there would be no deleterious effects. I always thought that was going to be the plan; that there would be some flag that would be set in struct super_block when the file system was exported that would enable i_version updates. That way we satisfy the "no extra configuration" needed requirement, which I agree is ideal, but we also don't waste any CPU overhead if the file system is not exported via NFSv4. I tried to implement anything along these lines because I don't care enough, and I don't use NFSv4 personally.... - Ted -- 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
