[Openib-windows] Using Netperf with WSD

[Tzachi Dar]

I have tested your fix and it works well.

Thanks
Tzachi 

> -----Original Message-----
> From: ftillier.sst at gmail.com [mailto:ftillier.sst at gmail.com] 
> On Behalf Of Fabian Tillier
> Sent: Monday, August 14, 2006 10:26 PM
> To: Tzachi Dar
> Cc: openib-windows at openib.org
> Subject: Re: [Openib-windows] Using Netperf with WSD
> 
> Hi Tzachi,
> 
> On 8/13/06, Tzachi Dar <tzachid at mellanox.co.il> wrote:
> >
> > Hi Fab,
> >
> > I have been trying to run netperf with WSD and the call to 
> duplicate 
> > socket fails there.
> > The main reason is probably the fact that the switch calls 
> > IBSPDuplicateSocket with a process id of a wrong process 
> (usually one 
> > of the svchosts).
> >
> > Still (ignoring this issue) it seems that there is a call to 
> > IBSPCloseSocket that calls 
> shutdown_and_destroy_socket_info. In this 
> > call, we have old_state == IBSP_DUPLICATING_OLD which 
> causes us to not 
> > do anything at the QP level, and therefore the code:
> >  while( socket_info->send_cnt || socket_info->recv_cnt )
> >   ib_cq_comp( socket_info->cq_tinfo ); keeps looping for ever. 
> > (recv_cnt is not 0)
> >
> > I have created a small patch that solves this problem (see bellow).
> 
> I just checked in a fix for this, revision 454.  It is 
> different than what you posted, as the error flow was 
> incorrect in the IBSPDuplicateSocket function.  The patch I 
> checked in will only change the state of the socket if all 
> the steps for duplication succeed locally.  This means that 
> if IBSPDuplicateSocket fails, the socket is left in the 
> connected state.
> 
> I also found a leak of the mapped view of the file handle, 
> and fixed that.
> 
> Please let me know if you see any issues with it.
> 
> Thanks,
> 
> - Fab
>