summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJeff Layton <jlayton@samba.org>2012-02-20 09:02:54 -0500
committerJeff Layton <jlayton@samba.org>2012-02-20 09:02:54 -0500
commit1c2f85a6aecffa7260709e5a44d77335bcade13f (patch)
tree73b10a21a7b7125b8e42f684fc1da09be129ae6c
parentc753cfe5491cfb1f1f74ca41444706383ab9f0e3 (diff)
downloadcifs-utils-1c2f85a6aecffa7260709e5a44d77335bcade13f.tar.gz
cifs-utils-1c2f85a6aecffa7260709e5a44d77335bcade13f.tar.bz2
cifs-utils-1c2f85a6aecffa7260709e5a44d77335bcade13f.zip
manpage: update wsize= entry to account for change in default wsize
Signed-off-by: Jeff Layton <jlayton@samba.org>
-rw-r--r--mount.cifs.84
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