summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/tuning/usesendfile.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/smbdotconf/tuning/usesendfile.xml')
-rw-r--r--docs/smbdotconf/tuning/usesendfile.xml17
1 files changed, 17 insertions, 0 deletions
diff --git a/docs/smbdotconf/tuning/usesendfile.xml b/docs/smbdotconf/tuning/usesendfile.xml
new file mode 100644
index 0000000000..e80598d463
--- /dev/null
+++ b/docs/smbdotconf/tuning/usesendfile.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="use sendfile"
+ context="S"
+ type="boolean"
+ xmlns:samba="http://samba.org/common">
+<description>
+ <para>If this parameter is <constant>yes</constant>, and Samba
+ was built with the --with-sendfile-support option, and the underlying operating
+ system supports sendfile system call, then some SMB read calls (mainly ReadAndX
+ and ReadRaw) will use the more efficient sendfile system call for files that
+ are exclusively oplocked. This may make more efficient use of the system CPU's
+ and cause Samba to be faster. This is off by default as it's effects are unknown
+ as yet. In particular, it appears that Windows 9X clients fail to work against
+ Samba with this parameter enabled in config.</para>
+</description>
+
+<value type="default">no</value>
+</samba:parameter>