Trond Myklebust wrote:
On Wed, 2009-09-09 at 22:47 +0100, James Pearson wrote:
The default behaviour with binary mount options when no [rw]size is to
select these preferred values - which to me, makes sense - as by not
giving a [rw]size, you are leaving it up the server to pick the 'best'
values for you - which I guess in most (all other?) cases happen to be
the maximum size.
Right. The above was indeed the guiding principle back when I did the
rsize/wsize negotiation for NFSv3 and NFSv2 for the binary mount code.
The NFS protocol specifies that the maximum values are there to tell you
that the server will do short read/writes if you exceed these. However,
the preferred values may correspond to a different 'sweet spot' for the
server read and write implementations.
So does that mean that the binary mount options are doing the right
thing, whereas the text mount options are not? Also, just to confirm,
I'm using NFSv3.
Thanks
James Pearson
--
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
