diff options
author | Yishai Hadas <yishaih@nvidia.com> | 2024-12-05 14:26:54 +0200 |
---|---|---|
committer | Alex Williamson <alex.williamson@redhat.com> | 2024-12-05 11:56:01 -0700 |
commit | 9c7c5430bca36e9636eabbba0b3b53251479c7ab (patch) | |
tree | 0be64e5865d7be9d779b19aef129a161bca85a8f /include/net/bonding.h | |
parent | 40384c840ea1944d7c5a392e8975ed088ecf0b37 (diff) | |
download | linux-9c7c5430bca36e9636eabbba0b3b53251479c7ab.tar.gz linux-9c7c5430bca36e9636eabbba0b3b53251479c7ab.tar.bz2 linux-9c7c5430bca36e9636eabbba0b3b53251479c7ab.zip |
vfio/mlx5: Align the page tracking max message size with the device capability
Align the page tracking maximum message size with the device's
capability instead of relying on PAGE_SIZE.
This adjustment resolves a mismatch on systems where PAGE_SIZE is 64K,
but the firmware only supports a maximum message size of 4K.
Now that we rely on the device's capability for max_message_size, we
must account for potential future increases in its value.
Key considerations include:
- Supporting message sizes that exceed a single system page (e.g., an 8K
message on a 4K system).
- Ensuring the RQ size is adjusted to accommodate at least 4
WQEs/messages, in line with the device specification.
The above has been addressed as part of the patch.
Fixes: 79c3cf279926 ("vfio/mlx5: Init QP based resources for dirty tracking")
Reviewed-by: Cédric Le Goater <clg@redhat.com>
Tested-by: Yingshun Cui <yicui@redhat.com>
Signed-off-by: Yishai Hadas <yishaih@nvidia.com>
Link: https://lore.kernel.org/r/20241205122654.235619-1-yishaih@nvidia.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'include/net/bonding.h')
0 files changed, 0 insertions, 0 deletions