Glad that this is fixed. I just verified that in vanilla 4.1.1, NFSv4.1 is performing well with parallel opens. We found this problem in our benchmarking study using 3.14.17. In case you are interested, we wrote a paper about NFSv4.1 benchmarking: http://www.fsl.cs.sunysb.edu/docs/nfs4perf/nfs4perf-sigm15.pdf Thanks, Ming On Thu, Jul 2, 2015 at 7:23 PM, Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> wrote: > On Thu, Jul 2, 2015 at 6:47 PM, Ming Chen <mchen@xxxxxxxxxxxxxxxxx> wrote: >> >> seqid, introduced in NFSv4.0, requires state-changing operations be performed >> synchronously, and thus limits parallelism. NFSv4.1 supports "unlimited >> parallelism" by using sessions and slots; seqid is no longer used and must be >> ignored by NFSv4.1 server. However, the current nfs client always call >> nfs_wait_on_seqid() no matter the version is 4.0 or 4.1. > > Please see commit 63f5f796af613 ("NFSv4.1: Allow parallel > OPEN/OPEN_DOWNGRADE/CLOSE") which first appeared in Linux-4.0. > > Cheers > Trond -- 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
