[NFS-Ganesha-Devel] Re: Scalability issue with VFS FSAL and large amounts of read i/o in flight
> But a certain someone wanted multiple requests on the same
socket to
> be concurrent, though that would mean some responses might finish out
> of order. (I've never thought that was a good idea.)
NFS clients do not require requests to finish in submit order. I don't understand
what this has to do with the price of wheat, though--only one thread is sending
on the socket at any time.
>
> Recently our maintainer was proposing that NFS Compound would also be
> parallelized. (I've never thought that was a good idea either.)
>
What can be parallelized is something the FSAL knows, not an absolute.
I want to also point out that asynchronous I/O is not very useful if the NFS4 Compound
processing can't be suspended. Note that the parallelization at the NFS v4 level is
NOT to parallelize the ops in a single compound (that wouldn't accomplish anything,
almost always each op depends on the previous op's results). The purpose is to allow
suspension of an in-progress protocol operation when it is calling an asynchronous capable
FSAL method which is not immediately returning. This of course will not be useful without
the ability to suspend an in-progress RPC request.
Frank