From 639a775866230fd1fb1a44d0f4e27522d9ade93a Mon Sep 17 00:00:00 2001 From: Christian Ambach Date: Fri, 30 Mar 2012 16:11:37 +0200 Subject: docs: update kernel oplocks documentation Signed-off-by: Jeremy Allison --- docs-xml/smbdotconf/locking/kerneloplocks.xml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'docs-xml/smbdotconf/locking') diff --git a/docs-xml/smbdotconf/locking/kerneloplocks.xml b/docs-xml/smbdotconf/locking/kerneloplocks.xml index c4f12b9bd4..9ac7256fb9 100644 --- a/docs-xml/smbdotconf/locking/kerneloplocks.xml +++ b/docs-xml/smbdotconf/locking/kerneloplocks.xml @@ -1,11 +1,13 @@ For UNIXes that support kernel based (currently only IRIX and the Linux 2.4 kernel), this parameter - allows the use of them to be turned on or off. + allows the use of them to be turned on or off. However, this disables + Level II oplocks for clients as the Linux and IRIX kernels do not + support them properly. Kernel oplocks support allows Samba oplocks to be broken whenever a local UNIX process or NFS operation @@ -13,6 +15,9 @@ 8 has oplocked. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a very cool feature :-). + If you do not need this interaction, you should disable the + parameter on Linux and IRIX to get Level II oplocks and the associated + performance benefit. This parameter defaults to on, but is translated to a no-op on systems that no not have the necessary kernel support. -- cgit