Whamcloud - gitweb
LU-10157 lnet: restore an maximal fragments count 85/37385/11
authorAlexey Lyashkov <c17817@cray.com>
Mon, 20 Apr 2020 18:42:50 +0000 (21:42 +0300)
committerOleg Drokin <green@whamcloud.com>
Tue, 16 Jun 2020 02:21:03 +0000 (02:21 +0000)
Lowering a number of fragments blocks a connection from older clients
who wantsto use 256 fragments to transfer. Let's restore this number
to the original value.

Fixes: 272e49ce2d5d ("LU-10157 lnet: make LNET_MAX_IOV dependent on page size")

Test-Parameters: trivial testlist=lnet-selftest,sanity-lnet
Cray-bug-id: LUS-8139
Signed-off-by: Alexey Lyashkov <c17817@cray.com>
Change-Id: Ia23aa1fb3d36a65abab6241c9ba75addc1dcce0a
Reviewed-on: https://review.whamcloud.com/37385
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Serguei Smirnov <ssmirnov@whamcloud.com>
Reviewed-by: Shaun Tancheff <shaun.tancheff@hpe.com>
Reviewed-by: James Simmons <jsimmons@infradead.org>
Reviewed-by: Oleg Drokin <green@whamcloud.com>

index 76ac7e3..c4b6222 100644 (file)
@@ -54,7 +54,8 @@
 /* Max payload size */
+/** limit on the number of fragments in discontiguous MDs */
+#define LNET_MAX_IOV   256
  * This is the maximum health value.