| commit | 3054252953a26d8f71f41d1f5cd3682fe11b9a2a | |
| author | Chuck Lever <chuck.lever@oracle.com> | |
| Thu, 22 Apr 2010 19:35:56 +0000 (22 15:35 -0400) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Wed, 12 May 2010 21:57:04 +0000 (12 14:57 -0700) | ||
| tree | 659b2ad8ae7061a7114df3d84e2ffd6844503acb | treesnapshot (tar.gz zip) |
| parent | c6322971f8013403e2ff5b7607ec4771b0c31949 | commitdiff |
NFS: rsize and wsize settings ignored on v4 mounts
commit 356e76b855bdbfd8d1c5e75bcf0c6bf0dfe83496 upstream.
NFSv4 mounts ignore the rsize and wsize mount options, and always use
the default transfer size for both. This seems to be because all
NFSv4 mounts are now cloned, and the cloning logic doesn't copy the
rsize and wsize settings from the parent nfs_server.
I tested Fedora's 2.6.32.11-99 and it seems to have this problem as
well, so I'm guessing that .33, .32, and perhaps older kernels have
this issue as well.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 356e76b855bdbfd8d1c5e75bcf0c6bf0dfe83496 upstream.
NFSv4 mounts ignore the rsize and wsize mount options, and always use
the default transfer size for both. This seems to be because all
NFSv4 mounts are now cloned, and the cloning logic doesn't copy the
rsize and wsize settings from the parent nfs_server.
I tested Fedora's 2.6.32.11-99 and it seems to have this problem as
well, so I'm guessing that .33, .32, and perhaps older kernels have
this issue as well.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| fs/nfs/client.c | diffblobblamehistory |