On Tue, Nov 10, 2015 at 12:44:13PM +0200, Sagi Grimberg wrote:
> Different devices may require different access permissions
> for rdma reads e.g. for Infiniband devices, local write access
> suffices while iWARP devices require remote write permissions as
> well.
>
> This situation generates extra logic for ULPs that need to be aware
> of the underlying device to determine rdma read access. Instead,
> add a device attribute for ULPs to use without being aware of the
> underlying device.
>
> Also, set rdma_read_access_flags in the relevant device drivers:
> mlx4, mlx5, qib, ocrdma, nes: IB_ACCESS_LOCAL_WRITE
> cxgb3, cxgb4, hfi: IB_ACCESS_LOCAL_WRITE | IB_ACCESS_REMOTE_WRITE
IB devices *should* be using a local_dma_lkey instead of a memory
registration for the RDMA READ target memory.
iWarp devices *must* use a memory registration instead.
Having an API that encourages ULPs to do useless MR work on IB does
not seem like a great idea, but if the ULP needs to create a MR anyhow
(SG limits or whatever), then it makes some sense.. But not in absence
of the 'need a mr' general check..
Finally, please don't add rdma_read_access_flags - we went to a lot of
trouble to add the cap stuff, and this stuff is already covered by it.
No need to change every driver.
I'd suggest something like
unsigned int rdma_cap_rdma_read_mr_flags(const struct ib_pd *pd)
{
if (rdma_protocol_iwarp(pd->device, rdma_start_port(pd->device)))
return IB_ACCESS_LOCAL_WRITE | IB_ACCESS_REMOTE_WRITE;
return IB_ACCESS_LOCAL_WRITE;
}
bool rdma_cap_need_rdma_read_mr(const struct ib_pd *pd) ...
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
