On Thu, 2019-09-19 at 18:58 +0300, Alkis Georgopoulos wrote: > On 9/19/19 6:08 PM, Trond Myklebust wrote: > > The default client behaviour is just to go with whatever > > recommended > > value the server specifies. You can change that value yourself on > > the > > knfsd server by editing the pseudo-file in > > /proc/fs/nfsd/max_block_size. > > Thank you, and I guess I can automate this, by running > `systemctl edit nfs-kernel-server`, and adding: > [Service] > ExecStartPre=sh -c 'echo 32768 > /proc/fs/nfsd/max_block_size' > > But isn't it a problem that the defaults cause errors in dmesg and > severe lags in 10/100 Mbps, and even make 1000 Mbps a lot less > snappy > than with 32K? > No. It is not a problem, because nfs-utils defaults to using TCP mounts. Fragmentation is only a problem with UDP, and we stopped defaulting to that almost 2 decades ago. However it may well be that klibc is still defaulting to using UDP, in which case it should be fixed. There are major Linux distros out there today that don't even compile in support for NFS over UDP any more. Cheers Trond -- Trond Myklebust Linux NFS client maintainer, Hammerspace trond.myklebust@xxxxxxxxxxxxxxx
