[openib-general] rdma_listen() backlog parameter

[Steve Wise]

The rnic might need to reserve resources based on the listen backlog, so
I think the kernel iwarp cma will need this.  This is rnic-dependent,
but at least the Ammasso rnic needs to know what the backlog should be.
For OpenIB, we _could_ lock this down to some fixed value on the iwarp
side.  

By the way, this listen backlog for an iwarp rnic is actually the
backlog of outstanding TCP connection requests as opposed to iwarp
connections.

Steve.

On Wed, 2005-11-16 at 11:54 -0800, Sean Hefty wrote:
> I've been trying to implement support for a backlog parameter in the CMA's
> rdma_listen() call.  My original goal was to push the backlog parameter down
> into the kernel CMA with the following definition:
> 
> Backlog - The number of unprocessed connection requests that a listener can
> have.  A connection request is considered processed once it has either been
> accepted or rejected.
> 
> To keep things simple, is there any reason for the kernel CMA to have a backlog
> parameter?  Would iWarp require this?  The kernel CMA is callback driven, which
> makes it trivial for clients to manage their own backlog.  I'm considering
> maintaining this within the kernel uCMA only, unless it would need to be pushed
> down for iWarp.
> 
> - Sean
> 
> _______________________________________________
> openib-general mailing list
> openib-general at openib.org
> http://openib.org/mailman/listinfo/openib-general
> 
> To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general