From c29eb90444170953721b087f8d26b4a3b98b3fe8 Mon Sep 17 00:00:00 2001 From: Alexander Bokovoy Date: Sun, 6 Apr 2003 22:14:01 +0000 Subject: 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) --- docs/docbook/smbdotconf/tuning/writecachesize.xml | 49 ++++++++++++----------- 1 file changed, 26 insertions(+), 23 deletions(-) (limited to 'docs/docbook/smbdotconf/tuning/writecachesize.xml') 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 @@ - - write cache size (S) - If this integer parameter is set to non-zero value, - Samba will create an in-memory cache for each oplocked file - (it does not 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. + + + If this integer parameter is set to non-zero value, + Samba will create an in-memory cache for each oplocked file + (it does not 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. - 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. + 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. - The integer parameter specifies the size of this cache - (per oplocked file) in bytes. + The integer parameter specifies the size of this cache + (per oplocked file) in bytes. - Default: write cache size = 0 - Example: write cache size = 262144 + Default: write cache size = 0 - for a 256k cache size per file. - - + Example: write cache size = 262144 + + for a 256k cache size per file. + + -- cgit