HP CIFS Client A.02.01 Administrator's Guide

Configuration File
Configuration Parameters
Chapter 7 109
requests. However, if your system's NFS client puts
high loads on NFS servers and has small maximum
socket buffer sizes, requests can get lost due to buffer
overflows. A value of 5 (which is also the default)
should be a good choice. You may want to experiment
with nfsTimeout to get the optimum performance even
with frequent buffer overflows.
nfsSockRxBuf
This integer variable sets the receive buffer size of the
socket used to communicate with the kernel. If the
value given is out of the acceptable range for your
machine, the HP CIFS Client automatically limits the
range. Increase the buffer size if you have extremely
slow writes.
nfsSockTxBuf This integer variable sets the transmit buffer size of
the socket used to communicate with the kernel. It is
not be necessary to set an explicit buffer size.
nfsTransferSize This integer variable defines the maximum block size
used in data transfer between the kernel and HP CIFS
Client. The maximum allowed value is 8k (8192). It
may be necessary to reduce the value if the NFS socket
has frequent overflows, as it may be the case with AIX
3.x. It is useful to use only powers of 2 as block sizes.
The default is 8192.
preferredPort This integer variable defines the port number that HP
CIFS Client attempts to use for NFS. If this port is not
available, the HP CIFS Client chooses a free one. It is
good to have a constant port for NFS because it allows
a restarted daemon to take over the mounts of a
previous incarnation. The port number must be below
1024 if not all local users are trusted.