aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/infiniband/core/security.c
diff options
context:
space:
mode:
authorMark Bloch <markb@mellanox.com>2017-11-02 15:22:26 +0200
committerDoug Ledford <dledford@redhat.com>2017-11-13 14:42:04 -0500
commit5f22a1d87c5315a98981ecf93cd8de226cffe6ca (patch)
treec2a0533bb5463c4e1806939d91e99146af97c7f3 /drivers/infiniband/core/security.c
parentIB/mlx4: Add contig support for control objects (diff)
downloadlinux-dev-5f22a1d87c5315a98981ecf93cd8de226cffe6ca.tar.xz
linux-dev-5f22a1d87c5315a98981ecf93cd8de226cffe6ca.zip
IB/mlx4: Increase maximal message size under UD QP
Maximal message should be used as a limit to the max message payload allowed, without the headers. The ConnectX-3 check is done against this value includes the headers. When the payload is 4K this will cause the NIC to drop packets. Increase maximal message to 8K as workaround, this shouldn't change current behaviour because we continue to set the MTU to 4k. To reproduce; set MTU to 4296 on the corresponding interface, for example: ifconfig eth0 mtu 4296 (both server and client) On server: ib_send_bw -c UD -d mlx4_0 -s 4096 -n 1000000 -i1 -m 4096 On client: ib_send_bw -d mlx4_0 -c UD <server_ip> -s 4096 -n 1000000 -i 1 -m 4096 Fixes: 6e0d733d9215 ("IB/mlx4: Allow 4K messages for UD QPs") Signed-off-by: Mark Bloch <markb@mellanox.com> Reviewed-by: Majd Dibbiny <majd@mellanox.com> Signed-off-by: Leon Romanovsky <leon@kernel.org> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'drivers/infiniband/core/security.c')
0 files changed, 0 insertions, 0 deletions