Dean Hildebrand wrote:
Thanks for the info Phil. While I'm running an I/O performance
experiment, I never want the attributes to expire, so I'm using the -a
option to set it to a really high value.
But for the average pvfs2 setup, what is a useful value? With 5msec,
the cache was continually
Thanks for the info Phil. While I'm running an I/O performance
experiment, I never want the attributes to expire, so I'm using the -a
option to set it to a really high value.
But for the average pvfs2 setup, what is a useful value? With 5msec,
the cache was continually expiring, and my data
Dean Hildebrand wrote:
Hi All,
I noticed my acache was never being used, and so I realized there is a
discrepancy between
#define ACACHE_DEFAULT_TIMEOUT_MSECS
5000
and the default timeout passed in to pvfs2-client (which is '-a 5').
Is the intention when using the kernel module to reset the
Hi All,
I noticed my acache was never being used, and so I realized there is a
discrepancy between
#define ACACHE_DEFAULT_TIMEOUT_MSECS
5000
and the default timeout passed in to pvfs2-client (which is '-a 5').
Is the intention when using the kernel module to reset the cache timeout
to 5msec
