[rdma-next,0/2] Set BlueFlame size based on memory properties
mbox series

Message ID 20191020064400.8344-1-leon@kernel.org
Headers show
  • Set BlueFlame size based on memory properties
Related show


Leon Romanovsky Oct. 20, 2019, 6:43 a.m. UTC
From: Leon Romanovsky <leonro@mellanox.com>


Libmlx5 needs real knowledge of BlueFlame size to properly set data
path to leverage performance advantages of BF. However such advantage
is visible in systems which use WC memory. Unfortunately, user space
applications (and libmlx5) can't know if memory is WC or not, so
we rely on in-kernel test to set BF dynamically.


Michael Guralnik (2):
  IB/mlx5: Align usage of QP1 create flags with rest of mlx5 defines
  IB/mlx5: Test write combining support

 drivers/infiniband/hw/mlx5/gsi.c     |   2 +-
 drivers/infiniband/hw/mlx5/main.c    |  15 +-
 drivers/infiniband/hw/mlx5/mem.c     | 200 +++++++++++++++++++++++++++
 drivers/infiniband/hw/mlx5/mlx5_ib.h |  13 +-
 drivers/infiniband/hw/mlx5/qp.c      |  12 +-
 5 files changed, 229 insertions(+), 13 deletions(-)