Changeset 988 for vendor/current/docs-xml/smbdotconf/tuning
- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- Location:
- vendor/current/docs-xml/smbdotconf/tuning
- Files:
-
- 2 added
- 1 deleted
- 19 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/smbdotconf/tuning/aioreadsize.xml
r414 r988 1 1 <samba:parameter name="aio read size" 2 2 context="S" 3 type="integer"3 type="bytes" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/aiowritesize.xml
r414 r988 1 1 <samba:parameter name="aio write size" 2 2 context="S" 3 type="integer"3 type="bytes" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/allocationroundupsize.xml
r414 r988 1 1 <samba:parameter name="allocation roundup size" 2 2 context="S" 3 type="integer"3 type="bytes" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/blocksize.xml
r414 r988 1 1 <samba:parameter name="block size" 2 type="integer"2 type="bytes" 3 3 context="S" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> -
vendor/current/docs-xml/smbdotconf/tuning/deadtime.xml
r414 r988 1 1 <samba:parameter name="deadtime" 2 2 context="G" 3 developer="1"4 3 type="integer" 5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> -
vendor/current/docs-xml/smbdotconf/tuning/getwdcache.xml
r414 r988 1 1 <samba:parameter name="getwd cache" 2 2 context="G" 3 developer="1"3 type="boolean" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/hostnamelookups.xml
r414 r988 2 2 context="G" 3 3 type="boolean" 4 advanced="1" developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/keepalive.xml
r414 r988 2 2 context="G" 3 3 type="integer" 4 advanced="1" developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> … … 14 13 has the SO_KEEPALIVE attribute set on it by default. (see <smbconfoption name="socket options"/>). 15 14 Basically you should only use this option if you strike difficulties.</para> 15 16 <para>Please note this option only applies to SMB1 client connections, and 17 has no effect on SMB2 clients.</para> 16 18 </description> 17 19 -
vendor/current/docs-xml/smbdotconf/tuning/maxdisksize.xml
r414 r988 1 1 <samba:parameter name="max disk size" 2 2 context="G" 3 type="integer" 4 developer="1" 3 type="bytes" 5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/maxopenfiles.xml
r414 r988 2 2 type="integer" 3 3 context="G" 4 advanced="1" developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> … … 8 7 open files that one <citerefentry><refentrytitle>smbd</refentrytitle> 9 8 <manvolnum>8</manvolnum></citerefentry> file 10 serving process may have open for a client at any one time. The11 This parameter can be set very high (16 404) as Samba uses9 serving process may have open for a client at any one time. 10 This parameter can be set very high (16384) as Samba uses 12 11 only one bit per unopened file. Setting this parameter lower than 13 16 404 will cause Samba to complain and set this value back to14 the minimum of 16 404, as Windows 7 depends on this number of12 16384 will cause Samba to complain and set this value back to 13 the minimum of 16384, as Windows 7 depends on this number of 15 14 open file handles being available.</para> 16 15 … … 20 19 </description> 21 20 22 <value type="default">16 404</value>21 <value type="default">16384</value> 23 22 </samba:parameter> -
vendor/current/docs-xml/smbdotconf/tuning/maxsmbdprocesses.xml
r414 r988 2 2 type="integer" 3 3 context="G" 4 developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/minprintspace.xml
r414 r988 2 2 context="S" 3 3 type="integer" 4 print="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/namecachetimeout.xml
r414 r988 2 2 context="G" 3 3 type="integer" 4 advanced="1" developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/socketoptions.xml
r414 r988 1 1 <samba:parameter name="socket options" 2 2 context="G" 3 type=" list"4 developer="1"3 type="string" 4 constant="1" 5 5 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 6 <description> 7 <para> 8 <warning> 9 <para>Modern server operating systems are tuned for high 10 network performance in the majority of situations; when you set socket 11 options you are overriding those settings. Linux in particular has an 12 auto-tuning mechanism for buffer sizes that will be disabled if you 13 specify a socket buffer size. This can potentially cripple your 14 TCP/IP stack.</para> 15 16 <para> Getting the socket options correct can make a big difference to 17 your performance, but getting them wrong can degrade it by just as 18 much. As with any other low level setting, if you must make changes 19 to it, make small changes and <emphasis>test</emphasis> the effect 20 before making any large changes.</para> 21 </warning> 22 </para> 23 7 24 <para>This option allows you to set socket options 8 25 to be used when talking with the client.</para> … … 24 41 either incorrectly typed it or you need to add an include file 25 42 to includes.h for your OS. If the latter is the case please 26 send the patch to <ulink url="mailto:samba-technical@ samba.org">27 samba-technical@ samba.org</ulink>.</para>43 send the patch to <ulink url="mailto:samba-technical@lists.samba.org"> 44 samba-technical@lists.samba.org</ulink>.</para> 28 45 29 46 <para>Any of the supported socket options may be combined … … 38 55 <listitem><para>SO_BROADCAST</para></listitem> 39 56 <listitem><para>TCP_NODELAY</para></listitem> 57 <listitem><para>TCP_KEEPCNT *</para></listitem> 58 <listitem><para>TCP_KEEPIDLE *</para></listitem> 59 <listitem><para>TCP_KEEPINTVL *</para></listitem> 40 60 <listitem><para>IPTOS_LOWDELAY</para></listitem> 41 61 <listitem><para>IPTOS_THROUGHPUT</para></listitem> 62 <listitem><para>SO_REUSEPORT</para></listitem> 42 63 <listitem><para>SO_SNDBUF *</para></listitem> 43 64 <listitem><para>SO_RCVBUF *</para></listitem> 44 65 <listitem><para>SO_SNDLOWAT *</para></listitem> 45 66 <listitem><para>SO_RCVLOWAT *</para></listitem> 67 <listitem><para>SO_SNDTIMEO *</para></listitem> 68 <listitem><para>SO_RCVTIMEO *</para></listitem> 69 <listitem><para>TCP_FASTACK *</para></listitem> 70 <listitem><para>TCP_QUICKACK</para></listitem> 71 <listitem><para>TCP_NODELAYACK</para></listitem> 72 <listitem><para>TCP_KEEPALIVE_THRESHOLD *</para></listitem> 73 <listitem><para>TCP_KEEPALIVE_ABORT_THRESHOLD *</para></listitem> 74 <listitem><para>TCP_DEFER_ACCEPT *</para></listitem> 46 75 </itemizedlist> 47 76 -
vendor/current/docs-xml/smbdotconf/tuning/strictallocate.xml
r740 r988 12 12 terminology this means that Samba will stop creating sparse files.</para> 13 13 14 <para>This option is really des gined for file systems that support14 <para>This option is really designed for file systems that support 15 15 fast allocation of large numbers of blocks such as extent-based file systems. 16 16 On file systems that don't support extents (most notably ext3) this can -
vendor/current/docs-xml/smbdotconf/tuning/strictsync.xml
r414 r988 6 6 <para>Many Windows applications (including the Windows 98 explorer 7 7 shell) seem to confuse flushing buffer contents to disk with doing 8 a sync to disk. Under UNIX, a sync call forces the processto be8 a sync to disk. Under UNIX, a sync call forces the thread to be 9 9 suspended until the kernel has ensured that all outstanding data in 10 10 kernel disk buffers has been safely stored onto stable storage. … … 18 18 addition, this fixes many performance problems that people have 19 19 reported with the new Windows98 explorer shell file copies.</para> 20 <para>The flush request from SMB2/3 clients is handled 21 asynchronously, so for these clients setting the parameter 22 to <constant>yes</constant> does not block the processing of other 23 requests in the smbd process.</para> 20 24 </description> 21 25 -
vendor/current/docs-xml/smbdotconf/tuning/usemmap.xml
r414 r988 2 2 context="G" 3 3 type="boolean" 4 developer="1"5 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 6 5 <description> -
vendor/current/docs-xml/smbdotconf/tuning/usesendfile.xml
r414 r988 2 2 context="S" 3 3 type="boolean" 4 function="_use_sendfile" 4 5 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 6 <description> … … 14 15 </description> 15 16 16 <value type="default"> false</value>17 <value type="default">no</value> 17 18 </samba:parameter> -
vendor/current/docs-xml/smbdotconf/tuning/writecachesize.xml
r414 r988 1 1 <samba:parameter name="write cache size" 2 2 context="S" 3 type="integer"3 type="bytes" 4 4 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc"> 5 5 <description> … … 22 22 <para>The integer parameter specifies the size of this cache 23 23 (per oplocked file) in bytes.</para> 24 25 <para>Note that the write cache won't be used for file handles with a smb2 write lease.</para> 24 26 </description> 25 27 28 <related>aio read size</related> 29 <related>aio write size</related> 30 <related>smb2 leases</related> 26 31 <value type="default">0</value> 27 32 <value type="example">262144<comment> for a 256k cache size per file</comment></value>
Note:
See TracChangeset
for help on using the changeset viewer.