Set BlueFlame size based on memory properties
Status from this message: Applied to for-next, thanks
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | IB/mlx5: Align usage of QP1 create flags with rest of mlx5 definesdrivers/ drivers/ drivers/ | +6 | 1 reply | |
| 2/2 | IB/mlx5: Test write combining supportdrivers/ drivers/ drivers/ +1 more | +224 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH rdma-next 0/2] Set BlueFlame size based on memory properties
From: Leon Romanovsky <[email protected]>
Hi,
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.
Thanks
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(-)
--
2.20.1