Chuck Lever wrote on 08/08/2018 12:01 PM:
On Aug 8, 2018, at 2:54 PM, admin@xxxxxxxxxxxxxxxxxx wrote:
Chuck Lever wrote on 07/14/2018 07:37 AM:
On Jul 13, 2018, at 6:32 PM, admin@xxxxxxxxxxxxxxxxxx wrote:
Chuck Lever wrote on 07/13/2018 07:36 AM:
You should be able to mount using "proto=tcp" with your mlx4 cards.
That avoids the use of NFS/RDMA but would enable the use of the
higher bandwidth network fabric.
Thanks I could definitely try that. IPoIB has it's own set of issues though but can cross that bridge when I get to it....
Stick with connected mode and keep rsize and wsize smaller
than the IPoIB MTU, which can be set as high as 65KB.
We are running in this setup, so far so good... however the rsize/wsize were much greater than the IPoIB MTU, and it is probably causing these "page allocation failures" which fortunately have not been fatal; our computation is still running. In the ifcfg file for the IPoIB interface, the MTU is set to 65520, which was the recommended maximum from the Red Hat manual. So should rsize/wsize be set to 65519? or is it better to pick another value that is a multiple 1024 or something?
The r/wsize settings have to be power of two. The next power of
two smaller than 65520 is 32768. Try "rsize=32768,wsize=32768" .
Thanks but what is the reason for that? After googling around a while
for rsize/wsize settings, i finally found in the nfs manual page (of all
places!!) that "If a specified value is within the supported range but
not a multiple of 1024, it is rounded down to the nearest multiple of
1024." So it sound like we could use 63KiB or 64512.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
