<snip>
You are right. But our idea is to provide an option to disable/enable
caching based on the nature of intended application.
[EH] Hear hear :-).
Our application consists of a number of machines collaborating on a shared
database over NFS. We therefore require the ability to force data to be
sync'd from the client to the backend - and at the moment we do this by
disabling caching completely, via the noac option and acquiring and
releasing non-exclusive locks round io calls.
Any improvements in the granularity of control over NFS client-side caching
would be very valuable to us.
Regards,
Edward Hibbert
Internet Applications Group
Data Connection Ltd
Tel: +44 131 662 1212 Fax: +44 131 662 1345
Email: eh@dataconnection.com Web: http://www.dataconnection.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/