With the proposed cifs.ko fix to honor maxmpx, cifs_max_pending because a limit when the server (as Windows often is) has more than 50 maxmpxct in its registry. Does anyone mind if I update the maximum to one or two hundred? (after the mpx fix is in)? On Wed, Oct 19, 2011 at 2:31 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote: > Signed-off-by: Jeff Layton <jlayton@xxxxxxxxxx> > --- > fs/cifs/cifsfs.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c > index b0a2e16..fa67245 100644 > --- a/fs/cifs/cifsfs.c > +++ b/fs/cifs/cifsfs.c > @@ -74,7 +74,7 @@ module_param(cifs_min_small, int, 0); > MODULE_PARM_DESC(cifs_min_small, "Small network buffers in pool. Default: 30 " > "Range: 2 to 256"); > unsigned int cifs_max_pending = CIFS_MAX_REQ; > -module_param(cifs_max_pending, int, 0); > +module_param(cifs_max_pending, int, 0444); > MODULE_PARM_DESC(cifs_max_pending, "Simultaneous requests to server. " > "Default: 50 Range: 2 to 256"); > unsigned short echo_retries = 5; > -- > 1.7.6.4 > > -- Thanks, Steve -- 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
