summaryrefslogtreecommitdiffstats
path: root/fs/hfs
diff options
context:
space:
mode:
authorAharon Landau <aharonl@nvidia.com>2022-07-31 11:26:36 +0300
committerLeon Romanovsky <leonro@nvidia.com>2022-08-16 15:21:52 +0300
commit13ad1125b941a5f257d9d3ae70485773abd34792 (patch)
tree2b04ccf944b5f81c6d93518d95d4c7ac996c5a23 /fs/hfs
parent19d6214ad6dfffda1a5bdc2b34ea75ba45a1a60a (diff)
downloadlinux-13ad1125b941a5f257d9d3ae70485773abd34792.tar.gz
linux-13ad1125b941a5f257d9d3ae70485773abd34792.tar.bz2
linux-13ad1125b941a5f257d9d3ae70485773abd34792.zip
RDMA/mlx5: Don't compare mkey tags in DEVX indirect mkey
According to the ib spec: If the CI supports the Base Memory Management Extensions defined in this specification, the L_Key format must consist of: 24 bit index in the most significant bits of the R_Key, and 8 bit key in the least significant bits of the R_Key Through a successful Allocate L_Key verb invocation, the CI must let the consumer own the key portion of the returned R_Key Therefore, when creating a mkey using DEVX, the consumer is allowed to change the key part. The kernel should compare only the index part of a R_Key to determine equality with another R_Key. Adding capability in order not to break backward compatibility. Fixes: 534fd7aac56a ("IB/mlx5: Manage indirection mkey upon DEVX flow for ODP") Link: https://lore.kernel.org/r/3d669aacea85a3a15c3b3b953b3eaba3f80ef9be.1659255945.git.leonro@nvidia.com Signed-off-by: Aharon Landau <aharonl@nvidia.com> Signed-off-by: Leon Romanovsky <leon@kernel.org>
Diffstat (limited to 'fs/hfs')
0 files changed, 0 insertions, 0 deletions