Ubuntu
linux package

~kerneltoast/ubuntu/+source/linux/+git/xenial:lp1874503

Git
lp:~kerneltoast/ubuntu/+source/linux/+git/xenial
lp1874503

Last commit made on 2020-06-04

Get this branch:: git clone -b lp1874503 https://git.launchpad.net/~kerneltoast/ubuntu/+source/linux/+git/xenial

Only Sultan Alsawaf can upload to this branch. If you are Sultan Alsawaf please log in for upload directions.

Branch merges

Branch information

Name:: lp1874503

Repository:: lp:~kerneltoast/ubuntu/+source/linux/+git/xenial

Recent commits

8c612e1... by Michael Guralnik <email address hidden> on 2019-06-10

IB/mlx5: Test write combining support

BugLink: https://bugs.launchpad.net/bugs/1874503

Linux can run in all sorts of physical machines and VMs where write
combining may or may not be supported. Currently there is no way to
reliably tell if the system supports WC, or not. The driver uses WC to
optimize posting work to the HCA, and getting this wrong in either
direction can cause a significant performance loss.

Add a test in mlx5_ib initialization process to test whether
write-combining is supported on the machine. The test will run as part of
the enable_driver callback to ensure that the test runs after the device
is setup and can create and modify the QP needed, but runs before the
device is exposed to the users.

The test opens UD QP and posts NOP WQEs, the WQE written to the BlueFlame
is different from the WQE in memory, requesting CQE only on the BlueFlame
WQE. By checking whether we received a completion on one of these WQEs we
can know if BlueFlame succeeded and this write-combining must be
supported.

Change reporting of BlueFlame support to be dependent on write-combining
support instead of the FW's guess as to what the machine can do.

Link: https://<email address hidden>
Signed-off-by: Michael Guralnik <email address hidden>
Signed-off-by: Leon Romanovsky <email address hidden>
Signed-off-by: Jason Gunthorpe <email address hidden>
(backported from commit 11f552e21755cb6f804572243a1502b6bbd008dd)
Signed-off-by: Sultan Alsawaf <email address hidden>

992d3f2... by Michael Guralnik <email address hidden> on 2019-10-20

IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines

BugLink: https://bugs.launchpad.net/bugs/1874503

There is little value in keeping separate function for one flag, provide
it directly like any other mlx5 define.

Link: https://<email address hidden>
Signed-off-by: Michael Guralnik <email address hidden>
Signed-off-by: Leon Romanovsky <email address hidden>
Reviewed-by: Jason Gunthorpe <email address hidden>
Signed-off-by: Jason Gunthorpe <email address hidden>
(cherry picked from commit 3f89b01f4bbab2dcd1a6e7e31e64faacb448e3be)
Signed-off-by: Sultan Alsawaf <email address hidden>

be6cb63... by Jason Gunthorpe <email address hidden> on 2019-02-13

RDMA/rxe: Close a race after ib_register_device

BugLink: https://bugs.launchpad.net/bugs/1874503

Since rxe allows unregistration from other threads the rxe pointer can
become invalid any moment after ib_register_driver returns. This could
cause a user triggered use after free.

Add another driver callback to be called right after the device becomes
registered to complete any device setup required post-registration. This
callback has enough core locking to prevent the device from becoming
unregistered.

Signed-off-by: Jason Gunthorpe <email address hidden>
(backported from commit ca22354b140853b8155692d5b2bc0110aa54e937)
Signed-off-by: Sultan Alsawaf <email address hidden>

5a40910... by Marcelo Cerri on 2020-05-25