From: Jenny Derzhavetz
We'll use remote invalidate, according to negotiation result
during connection establishment. If the initiator declared that
it supports the remote invalidate exception then the target will
use IB_WR_SEND_WITH_INV with the correct rkey for the response.
Signed-off-by: Jenn
On 11/16/2015 6:37 PM, Sagi Grimberg wrote:
We'll use remote invalidate, according to negotiation result
during connection establishment. If the initiator declared that
it supports the remote invalidate exception then the target will
use IB_WR_SEND_WITH_INV with the correct rkey for the response.
On 17/11/2015 10:09, Or Gerlitz wrote:
On 11/16/2015 6:37 PM, Sagi Grimberg wrote:
We'll use remote invalidate, according to negotiation result
during connection establishment. If the initiator declared that
it supports the remote invalidate exception then the target will
use IB_WR_SEND_WITH_I
On 11/17/2015 11:50 AM, Sagi Grimberg wrote:
same comment as the one I posted for the initiator patch, check for
IB_DEVICE_MEM_MGT_EXTENSIONS
SEND_WITH_INV doesn't have anything to do with
IB_DEVICE_MEM_MGT_EXTENSIONS does it? What is the relations between
the device capability to do FRWR and
On Tue, Nov 17, 2015 at 11:50:15AM +0200, Sagi Grimberg wrote:
>
>
> On 17/11/2015 10:09, Or Gerlitz wrote:
> >On 11/16/2015 6:37 PM, Sagi Grimberg wrote:
> >>We'll use remote invalidate, according to negotiation result
> >>during connection establishment. If the initiator declared that
> >>it su
On 17/11/2015 12:14, Christoph Hellwig wrote:
On Tue, Nov 17, 2015 at 11:50:15AM +0200, Sagi Grimberg wrote:
On 17/11/2015 10:09, Or Gerlitz wrote:
On 11/16/2015 6:37 PM, Sagi Grimberg wrote:
We'll use remote invalidate, according to negotiation result
during connection establishment. If t
On 11/16/2015 6:37 PM, Sagi Grimberg wrote:
struct isert_conn *conn;
@@ -209,6 +210,7 @@ struct isert_conn {
struct work_struct release_work;
struct ib_recv_wr beacon;
boollogout_posted;
+ boolsnd_w_inv
