On Wed, Aug 05, 2015 at 05:13:22PM -0400, Jeff Layton wrote: > Currently, NFSv2/3 reads and writes have to open a file, do the read or > write and then close it again for each RPC. This is highly inefficient, > especially when the underlying filesystem has a relatively slow open > routine. .. as do many NFSv4 reads and writes as they often get special stateids passed from the client. Seems a little odd that we take more care of this for the legacy protocols than the current one. I think I'd rather see a nfs4_file cache and turn v2/3 into something like the special stateid case. Did you consider that? -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
