We have raised this issue before, but it can start becoming
more acute with the time.
- In ib_query_ca(), we need to retrieve the vendor-specific
info (e.g., the FW version). This is desirable for achieving
compatibility between our chip generations. We cannot commit
what kind/size of info we'd like to expose to the user app,
so we prefer IBAL to manipulate an opaque buffer for that.
- In ib_query_qp(), we need to retrieve the maximum size
allowed for inline sends for this QP.
Currently, IBAL has made inline sends explicit, but the user
has no way to compute the allowed size. We provide a
proprietary macro for that (that computes the size based on
the number of the S/G entries supported by the send queue),
but prefer to let the user receive the info in an opaque
buffer through ib_query_qp() because in the future chip
generations the computation may be more complex.
So, can any query type have a vendor-specific buffer?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=742384
We have raised this issue before, but it can start becoming
more acute with the time.
- In ib_query_ca(), we need to retrieve the vendor-specific
info (e.g., the FW version). This is desirable for achieving
compatibility between our chip generations. We cannot commit
what kind/size of info we'd like to expose to the user app,
so we prefer IBAL to manipulate an opaque buffer for that.
- In ib_query_qp(), we need to retrieve the maximum size
allowed for inline sends for this QP.
Currently, IBAL has made inline sends explicit, but the user
has no way to compute the allowed size. We provide a
proprietary macro for that (that computes the size based on
the number of the S/G entries supported by the send queue),
but prefer to let the user receive the info in an opaque
buffer through ib_query_qp() because in the future chip
generations the computation may be more complex.
So, can any query type have a vendor-specific buffer?
Logged In: YES
user_id=784019
Note that the Mellanox driver does not return the QP
attributes when calling create QP.