diff options
author | Alexander Bokovoy <ab@samba.org> | 2003-04-06 22:14:01 +0000 |
---|---|---|
committer | Alexander Bokovoy <ab@samba.org> | 2003-04-06 22:14:01 +0000 |
commit | c29eb90444170953721b087f8d26b4a3b98b3fe8 (patch) | |
tree | 257b1ee9b093a057b81e289fd511b992cc518642 /docs/docbook/smbdotconf/tuning/writecachesize.xml | |
parent | 27aef6855f1543547b8190f06fd264d1b52a558d (diff) | |
download | samba-c29eb90444170953721b087f8d26b4a3b98b3fe8.tar.gz samba-c29eb90444170953721b087f8d26b4a3b98b3fe8.tar.bz2 samba-c29eb90444170953721b087f8d26b4a3b98b3fe8.zip |
Convert more parameters to new smb.conf(5) style. Document found occurences of non-documented parameters in doc-status
(This used to be commit 3a9784d8b2318af4d9b349edd1aba4065d25da23)
Diffstat (limited to 'docs/docbook/smbdotconf/tuning/writecachesize.xml')
-rw-r--r-- | docs/docbook/smbdotconf/tuning/writecachesize.xml | 49 |
1 files changed, 26 insertions, 23 deletions
diff --git a/docs/docbook/smbdotconf/tuning/writecachesize.xml b/docs/docbook/smbdotconf/tuning/writecachesize.xml index b54a0e4fd6..8b5fbe66bd 100644 --- a/docs/docbook/smbdotconf/tuning/writecachesize.xml +++ b/docs/docbook/smbdotconf/tuning/writecachesize.xml @@ -1,27 +1,30 @@ -<samba:parameter xmlns:samba="http://samba.org/common"> - <term><anchor id="WRITECACHESIZE"/>write cache size (S)</term> - <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> +<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>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>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>Default: <command moreinfo="none">write cache size = 0</command></para> - <para>for a 256k cache size per file.</para> - </listitem> - </samba:parameter> + <para>Example: <command moreinfo="none">write cache size = 262144</command></para> + + <para>for a 256k cache size per file.</para> +</listitem> +</samba:parameter> |