Date: Sat, 16 Sep 2023 17:51:48 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 267631] slow nfs from FreeBSD guest/client to linux host/server Message-ID: <bug-267631-3630-LUCse7djH0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-267631-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-267631-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D267631 --- Comment #3 from Vladimir Druzenko <vvd@FreeBSD.org> --- BTW, man page mount_nfs says that 4 is max value and 0 is allowed: readahead=3D=E2=9F=A8value=E2=9F=A9 Set the read-ahead count to the specified value. This may be in the range of 0 - 4, and determines how many blocks will be read ahead when a large file is being r= ead sequentially. Trying a value greater than 1 for this = is suggested for mounts with a large bandwidth * delay product. With value 0 mount_nfs print error message and exit. And max value is 16 no= w, not 4. IMHO, better to increase this value for at least 128 (or even 1024 to "cove= r" more than 10GE). I can't test patches to kernel often: I have 2 hosts with 10GE and both are= in production. One more question to fs@: is it possible to set default readahead on server side? P.S. This may be a topic for another PR, but maybe I'll create one later if someone from fs@ asks for it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-267631-3630-LUCse7djH0>