diff options
| author |   Honggang Li <honli@redhat.com> | 2019-09-28 01:43:52 +0800 |
|---|---|---|
| committer |   Jason Gunthorpe <jgg@mellanox.com> | 2019-10-08 15:17:32 -0300 |
| commit | b2e872f451992e5ac3d6b79a62b66f1721e29521 (patch) | |
| tree | 03d158430659baa75f37cbb5b465566beb4a5943 /drivers/infiniband/hw/bnxt_re/main.c | |
| parent | RDMA/srp: Add parse function for maximum initiator to target IU size (diff) | |
| download | linux-dev-b2e872f451992e5ac3d6b79a62b66f1721e29521.tar.xz linux-dev-b2e872f451992e5ac3d6b79a62b66f1721e29521.zip | |
RDMA/srp: Calculate max_it_iu_size if remote max_it_iu length available
The default maximum immediate size is too big for old srp clients, which
do not support immediate data.
According to the SRP and SRP-2 specifications, the IOControllerProfile
attributes for SRP target ports contains the maximum initiator to target
iu length.
The maximum initiator to target iu length can be obtained by sending MAD
packets to query subnet manager port and SRP target ports. We should
calculate the max_it_iu_size instead of the default value, when remote
maximum initiator to target iu length available.
Link: https://lore.kernel.org/r/20190927174352.7800-2-honli@redhat.com
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Honggang Li <honli@redhat.com>
Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions