[PATCH 0/2] IB/iSER: Calculating the VA in iSER header

The following patch set includes a bug fix for the VA value in the iSER header. The current value is incorrect according to the iSER spec. This patch set includes a bug fix for the initiator code that was made against the 2.6.26 branch and a fix for the iSER code in STGT. --~--~-~--~~-

[PATCH 1/2] IB/iSER: Do not add unsolicited data offset to VA in iSER header

iSER initiator sends a VA (in the iSER header) which includes an offset for the unsolicited data (which is wrong according to the spec). Signed-off-by: Eli Dorfman <[EMAIL PROTECTED]> Signed-off-by: Erez Zilber <[EMAIL PROTECTED]> --- drivers/infiniband/ulp/iser/iser_initiator.c |6 +++--- 1

[PATCH 2/2] IB/iSER: Use offset from r2t header for rdma

Use offset from r2t header for rdma instead of using internal offset counter. Signed-off-by: Eli Dorfman <[EMAIL PROTECTED]> --- usr/iscsi/iscsi_rdma.c | 16 +--- 1 files changed, 5 insertions(+), 11 deletions(-) diff --git a/usr/iscsi/iscsi_rdma.c b/usr/iscsi/iscsi_rdma.c index d

Publishing iSER limitations

This new thread summarizes and continues a discussion that we (Mike, Or and myself) had outside the list. This is what we have so far: * Having a parent device: commit 62786b526687db54c6dc22a1786d6df8b03da3f3 in the bnx2i branch looks ok, and will solve the DMA mask problem. I thi

Re: support for multiple initiator names and iser ifaces

Mike Christie wrote: > Hey Erez and Or and list, > > I do not remember which one of you requested it, but I added code to > support multiple initiator names. You can create multiple sessions from > the same host to the same target portal. It is in the head of the > open-iscsi git tree. This cou

Re: detected conn error (1011) on login with open-iscsi-2.0-869

On 23 Apr, 20:29, Mike Christie <[EMAIL PROTECTED]> wrote: > DaMn wrote: > > Hi, > > > despite the Subject, i've not found a solution to my problem in others > > threads. > > I'm having trouble connecting a target with two LUN: > > > # iscsiadm -m discovery -t st -p 192.168.29.13 > > puts out: >

RE: [ofa-general] [PATCH 2/2] IB/iSER: Use offset from r2t header forrdma

> > usr/iscsi/iscsi_rdma.c | 16 +--- > > I have no idea what tree this file lives in so I'll just ignore this > patch, right? As Eli mentioned in PATCH 0/2, the patch set contains a fix for the initiator side and another fix for the iSER code in stgt. That's why Fujita Tomonori (

RE: [PATCH 1/2] IB/iSER: Do not add unsolicited data offset to VA in iSER header

> So what was the conclusion on the right way to handle the change that > affects on-the-wire data? Just have a flag day so targets either work > with 2.6.25 and earlier initiators, or work with 2.6.26 and later > initiators, and corrupt data if someone mixes things the wrong way? See Eli's answ

Re: Publishing iSER limitations

Erez Zilber wrote: > This new thread summarizes and continues a discussion that we (Mike, Or > and myself) had outside the list. This is what we have so far: > > * Having a parent device: commit > 62786b526687db54c6dc22a1786d6df8b03da3f3 in the bnx2i branch looks > ok, and will so

Re: Publishing iSER limitations

Erez Zilber wrote: > This new thread summarizes and continues a discussion that we (Mike, Or > and myself) had outside the list. This is what we have so far: > > * Having a parent device: commit > 62786b526687db54c6dc22a1786d6df8b03da3f3 in the bnx2i branch looks > ok, and will so

Re: Publishing iSER limitations

Mike Christie wrote: > Erez Zilber wrote: >> This new thread summarizes and continues a discussion that we (Mike, Or >> and myself) had outside the list. This is what we have so far: >> >> * Having a parent device: commit >> 62786b526687db54c6dc22a1786d6df8b03da3f3 in the bnx2i branch lo