Revision 6d20e8406f0942228a73000663c2b33f488103ea authored by Suresh Jayaraman on 01 December 2010, 09:12:28 UTC, committed by Steve French on 02 December 2010, 19:32:11 UTC
Currently, the attribute cache timeout for CIFS is hardcoded to 1 second. This means that the client might have to issue a QPATHINFO/QFILEINFO call every 1 second to verify if something has changes, which seems too expensive. On the other hand, if the timeout is hardcoded to a higher value, workloads that expect strict cache coherency might see unexpected results. Making attribute cache timeout as a tunable will allow us to make a tradeoff between performance and cache metadata correctness depending on the application/workload needs. Add 'actimeo' tunable that can be used to tune the attribute cache timeout. The default timeout is set to 1 second. Also, display actimeo option value in /proc/mounts. It appears to me that 'actimeo' and the proposed (but not yet merged) 'strictcache' option cannot coexist, so care must be taken that we reset the other option if one of them is set. Changes since last post: - fix option parsing and handle possible values correcly Reviewed-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Suresh Jayaraman <sjayaraman@suse.de> Signed-off-by: Steve French <sfrench@us.ibm.com>
1 parent 8cb280c
File | Mode | Size |
---|---|---|
hw_breakpoint | ||
kdb | ||
kfifo | ||
kobject | ||
kprobes | ||
trace_events | ||
tracepoints | ||
Kconfig | -rw-r--r-- | 1.7 KB |
Makefile | -rw-r--r-- | 140 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...