linux-stable.git/drivers/infiniband/ulp/iser, branch linux-4.8.y

IB/core: Enhance ib_map_mr_sg()

2016-05-13T17:37:57+00:00

The SRP initiator allows to set max_sectors to a value that exceeds
the largest amount of data that can be mapped at once with an mlx4
HCA using fast registration and a page size of 4 KB. Hence modify
ib_map_mr_sg() such that it can map partial sg-elements. If an
sg-element has been mapped partially, let the caller know
which fraction has been mapped by adjusting *sg_offset.

Signed-off-by: Bart Van Assche 
Tested-by: Laurence Oberman 
Cc: Christoph Hellwig 
Cc: Sagi Grimberg 
Signed-off-by: Doug Ledford

IB/core: Add passing an offset into the SG to ib_map_mr_sg

2016-05-13T17:37:11+00:00

Signed-off-by: Christoph Hellwig 
Tested-by: Steve Wise 
Reviewed-by: Bart Van Assche 
Reviewed-by: Sagi Grimberg 
Reviewed-by: Steve Wise 
Signed-off-by: Doug Ledford

IB/iser: Fix max_sectors calculation

2016-05-05T16:41:24+00:00

iSER currently has a couple places that set max_sectors in either the host
template or SCSI host, and all of them get it wrong.

This patch instead uses a single assignment that (hopefully) gets it right:
the max_sectors value must be derived from the number of segments in the
FR or FMR structure, but actually be one lower than the page size multiplied
by the number of sectors, as it has to handle the case of non-aligned I/O.

Without this I get trivial to reproduce hangs when running xfstests
(on XFS) over iSER to Linux targets.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Max Gurtovoy 
Acked-by: Sagi Grimberg 
Signed-off-by: Doug Ledford

Merge branches 'mlx4', 'mlx5' and 'ocrdma' into k.o/for-4.6

2016-03-16T17:38:28+00:00

iser: Accept arbitrary sg lists mapping if the device supports it

2016-03-04T16:59:35+00:00

If the device support arbitrary sg list mapping (device cap
IB_DEVICE_SG_GAPS_REG set) we allocate the memory regions with
IB_MR_TYPE_SG_GAPS and allow the block layer to pass us
gaps by skip setting the queue virt_boundary.

Signed-off-by: Sagi Grimberg 
Signed-off-by: Doug Ledford

IB/iser: Use ib_drain_sq()

2016-02-29T22:10:27+00:00

Signed-off-by: Steve Wise 
Signed-off-by: Doug Ledford

IB/iser: Support the remote invalidation exception

2015-12-27T00:27:10+00:00

Declare that we support remote invalidation in case we are:
1. using fastreg method
2. always registering memory

Detect the invalidated rkey from the work completion info so we
won't invalidate it locally. The spec mandates that we must not rely
on the target remote invalidate our rkey so we must check it upon
a receive (scsi response) completion.

Signed-off-by: Jenny Derzhavetz 
Signed-off-by: Sagi Grimberg 
Signed-off-by: Doug Ledford

IB/iser: Change the increment rkey flow logic

2015-12-24T05:17:36+00:00

When we enable remote invalidate support we won't want to perform
local invalidates at the same time we do today, but we still need
to get new rkeys.  So, decouple the rkey update from the local
invalidate and tie it to memory reg instead.

Signed-off-by: Sagi Grimberg 
Signed-off-by: Jenny Derzhavetz 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Doug Ledford

IB/iser,isert: Create and use new shared header

2015-12-24T05:17:35+00:00

The iser RDMA_CM negotiation protocol is shared by
the initiator and the target, so have a shared header
for the defines and structure. Move relevant items from
the initiator and target headers.

Signed-off-by: Sagi Grimberg 
Signed-off-by: Jenny Derzhavetz 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Doug Ledford

IB/iser: set intuitive values for mr_valid

2015-12-24T05:17:34+00:00

This parameter is described as "is mr valid indicator".
In other words, it indicates whether memory registration
is valid or not. So intuitive values would be:
mr_valid=True, when memory registration is valid and
mr_valid=False otherwise.

Signed-off-by: Jenny Derzhavetz 
Signed-off-by: Sagi Grimberg 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Doug Ledford