On Mon, 20 Feb 2012 09:04:06 -0500 Jeff Layton <jlayton@xxxxxxxxx> wrote: > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxx> > --- > mount.cifs.8 | 4 +++- > 1 files changed, 3 insertions(+), 1 deletions(-) > > diff --git a/mount.cifs.8 b/mount.cifs.8 > index 74aa061..1f07d2c 100644 > --- a/mount.cifs.8 > +++ b/mount.cifs.8 > @@ -457,7 +457,9 @@ Maximum amount of data that the kernel will request in a read request in bytes. > .PP > wsize=\fIbytes\fR > .RS 4 > -Maximum amount of data that the kernel will send in a write request in bytes\&. Prior to kernel 3\&.0\&.0, the default and maximum was 57344 (14 * 4096 pages)\&. As of 3\&.0\&.0, the default is 1M, and the maximum allowed is 16M\&. Note that this value is just a starting point for negotiation in 3\&.0\&.0 and up\&. The client and server may negotiate this size downward according to the server's capabilities\&. In kernels prior to 3\&.0\&.0, no negotiation is performed\&. It can end up with an existing superblock if this value isn't specified or it's greater or equal than the existing one\&. > +Maximum amount of data that the kernel will send in a write request in bytes\&. Prior to kernel 3\&.0\&.0, the default and maximum was 57344 (14 * 4096 pages)\&. As of 3\&.0\&.0, the default depends on whether the client and server negotiate large writes via POSIX extensions. If they do, then the default is 1M, and the maximum allowed is 16M\&. If they do not, then the default is 65536 and the maximum allowed is 131007. > +.PP > +Note that this value is just a starting point for negotiation in 3\&.0\&.0 and up\&. The client and server may negotiate this size downward according to the server's capabilities\&. In kernels prior to 3\&.0\&.0, no negotiation is performed\&. It can end up with an existing superblock if this value isn't specified or it's greater or equal than the existing one\&. > .RE > .PP > fsc Committed... -- Jeff Layton <jlayton@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
