[linux-cifs-client] cifs client commands/requests timeout values

Shirish Pargaonkar shirishpargaonkar at gmail.com
Wed May 12 09:04:51 MDT 2010


Is it reasonable for a std op command like get path info to expect response
in 15 seconds when it happens to be a 50th command lined up behind
49 long op commands like 56 KBytes reads/writes.


        if (long_op == CIFS_STD_OP)
                timeout = 15 * HZ;
        else if (long_op == CIFS_VLONG_OP) /* e.g. slow writes past EOF */
                timeout = 180 * HZ;
        else if (long_op == CIFS_LONG_OP)
                timeout = 45 * HZ; /* should be greater than

Should not timeout value be calculated value based on some criterion
like what_kind_of and how_many commands/requests are in the pipeline
on that socket at the client end?

Above timeout values are reasonable if an individual command was the
only command/request sent.

Regards,

Shirish


More information about the linux-cifs-client mailing list