Re: [PATCH RFC 1/3] IB/core: Expose a device attribute for rdma_read access flags

[Sagi Grimberg <sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>]

On 10/11/2015 15:41, Christoph Hellwig wrote:
> FYI, this is the API I'd aim for (only SRP and no HW driver converted
> yet):

This looks fine, although personally I find scope and direction flags
more confusing than access_flags (but maybe it's just me).

I think that the real issue here is the server/target side which needs
extra logic for rdma_read and memory registration. If we can put this
logic in the core and give ULPs an API that looks something like:
- ib_rdma_read()
- ib_rdma_write()

then maybe we don't need to change our flags?

The only reason why I posted this series was a pre-step for this type
of API so we can avoid the is_iwarp() condition in the hot path.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html