diff options
Diffstat (limited to 'docs/docbook/smbdotconf/tuning/writecachesize.xml')
| -rw-r--r-- | docs/docbook/smbdotconf/tuning/writecachesize.xml | 30 |
1 files changed, 0 insertions, 30 deletions
diff --git a/docs/docbook/smbdotconf/tuning/writecachesize.xml b/docs/docbook/smbdotconf/tuning/writecachesize.xml deleted file mode 100644 index 8b5fbe66bd..0000000000 --- a/docs/docbook/smbdotconf/tuning/writecachesize.xml +++ /dev/null @@ -1,30 +0,0 @@ -<samba:parameter name="write cache size" - context="S" - xmlns:samba="http://samba.org/common"> -<listitem> - <para>If this integer parameter is set to non-zero value, - Samba will create an in-memory cache for each oplocked file - (it does <emphasis>not</emphasis> do this for - non-oplocked files). All writes that the client does not request - to be flushed directly to disk will be stored in this cache if possible. - The cache is flushed onto disk when a write comes in whose offset - would not fit into the cache or when the file is closed by the client. - Reads for the file are also served from this cache if the data is stored - within it.</para> - - <para>This cache allows Samba to batch client writes into a more - efficient write size for RAID disks (i.e. writes may be tuned to - be the RAID stripe size) and can improve performance on systems - where the disk subsystem is a bottleneck but there is free - memory for userspace programs.</para> - - <para>The integer parameter specifies the size of this cache - (per oplocked file) in bytes.</para> - - <para>Default: <command moreinfo="none">write cache size = 0</command></para> - - <para>Example: <command moreinfo="none">write cache size = 262144</command></para> - - <para>for a 256k cache size per file.</para> -</listitem> -</samba:parameter> |