Before we expose any new opcodes to userspace we need to actually
move the defintions of user visible opcodes to a uapi header. Without
that we're doomed to regularly break the ABI.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majord...@vger.
On 16/11/2015 19:02, Christoph Hellwig wrote:
On Mon, Nov 16, 2015 at 07:00:06PM +0200, Sagi Grimberg wrote:
Remove the unused ib_allow_mw and ib_bind_mw functions, remove the
unused IB_WR_BIND_MW and IB_WC_BIND_MW opcodes and move ib_dealloc_mw
into the uverbs module.
Signed-off-by: Christ
On Mon, Nov 16, 2015 at 07:00:06PM +0200, Sagi Grimberg wrote:
>
>> Remove the unused ib_allow_mw and ib_bind_mw functions, remove the
>> unused IB_WR_BIND_MW and IB_WC_BIND_MW opcodes and move ib_dealloc_mw
>> into the uverbs module.
>>
>> Signed-off-by: Christoph Hellwig
>
> Will the user-space
Remove the unused ib_allow_mw and ib_bind_mw functions, remove the
unused IB_WR_BIND_MW and IB_WC_BIND_MW opcodes and move ib_dealloc_mw
into the uverbs module.
Signed-off-by: Christoph Hellwig
Will the user-space drivers posting via uverbs (qib, hfi, rxe) need the
post_send interface?
--
To
Remove the unused ib_allow_mw and ib_bind_mw functions, remove the
unused IB_WR_BIND_MW and IB_WC_BIND_MW opcodes and move ib_dealloc_mw
into the uverbs module.
Signed-off-by: Christoph Hellwig
---
Documentation/infiniband/core_locking.txt | 2 -
drivers/infiniband/core/uverbs.h|
