Managing NFS and KRPC Kernel Configurations in HP-UX 11i v3 (762807-001, March 2014)

Restrictions on Changing
Modifying the Value
If server functionality depends upon clusters of operations coming from the client, increase the value of
this tunable. However, this increase impacts the operations in other queues if they have to wait until
the current queue is empty or the cluster limit is reached.
Note: Setting the value of nfs4_async_clusters to 0 causes all
of the queued requests of a particular type to be processed
before moving to the next type.
2.1.34 nfs4_bsize
Description
The nfs4_bsize tunable controls the logical block size used by NFSv4 clients. Block size represents the
amount of data the client reads from or writes to the server.
The nfs4_bsize tunable works in conjunction with the nfs4_max_transfer_size and
nfs4_max_transfer_size_cots tunables when determining the maximum size of these I/O requests. For
NFSv4 TCP traffic, the transfer size corresponds to the smallest value of nfs4_bsize,
nfs4_max_transfer_size, and nfs4_max_transfer_size_cots.
The nfs2_bsize tunable controls the logical block size used by NFSv2 clients. The nfs3_bsize tunable
controls the logical block size used by NFSv3 clients. For more information on these tunables, see:
• nfs2_bsize
• nfs3_bsize
Tested Values
Default: 32768
Min: 4096
Max: 1048576
Note: If the tunable is set to a value greater than 1048576
bytes, an informational warning is issued, at runtime. Any
value greater than 1048576 is outside the tested limits. The
value of the tunable must be a power of 2.