[Lustre-devel] lustre-1.8.8: rdma_listen() backlog 0 breaks iWARP
swise at opengridcomputing.com
Thu Jul 24 08:13:50 PDT 2014
> > I'm not sure why it was changed to 0 though. It definitely breaks iwarp
> > support. I'm not
> > yet sure what the semantics are for creating a listening cm_id with a
> > backlog of 0. Was
> > the assumption that 0 means "let the system choose" or "max supported
> > backlog"? The iwarp
> > CM interprets 0 to mean no connection requests allowed. :)
> 0 should mean let the system choose. Interpreting 0 as no connections allowed doesn't
> really make sense, since the app can get that by not calling listen at all.
Ok then we can fix this in the iwcm. I'll post a patch to Linux-rdma soon.
More information about the lustre-devel