summaryrefslogtreecommitdiffstats
path: root/drivers/clk
diff options
context:
space:
mode:
authorMark Bloch <markb@mellanox.com>2017-11-02 15:22:26 +0200
committerBen Hutchings <ben@decadent.org.uk>2018-02-13 18:42:21 +0000
commite63ac7ca2b879aee79f3fd325622d861a5ab6078 (patch)
tree41d562da79696e116a8f0e9fe76c27cb21103ccd /drivers/clk
parent97141d69b6111cead4710fdfb32b9f8559ad37b2 (diff)
downloadlinux-stable-e63ac7ca2b879aee79f3fd325622d861a5ab6078.tar.gz
linux-stable-e63ac7ca2b879aee79f3fd325622d861a5ab6078.tar.bz2
linux-stable-e63ac7ca2b879aee79f3fd325622d861a5ab6078.zip
IB/mlx4: Increase maximal message size under UD QP
commit 5f22a1d87c5315a98981ecf93cd8de226cffe6ca upstream. 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> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'drivers/clk')
0 files changed, 0 insertions, 0 deletions