[openib-general] IBM eHCA testing..

[Troy Benjegerdes]

What is the turnaround time on a firmware change? If we can get an
update, I think that would be the best solution. I'll be happy to test
this.

On Wed, Oct 12, 2005 at 11:36:59AM +0200, IBMEHCA DD wrote:
> This is basically the answer why its so "sensitive" which port is plugged.
> We're working on a solution to that problem.
> But currently we only see a chance to change this behaviour by also 
> changing the firmware interface,
> which needs to be coordinated with firmware development.
> 
> Roland Dreier wrote on 10.10.2005 23:44:21:
> 
> > IBMEHCA> So you need some kind of signal from the operating system
> > IBMEHCA> to system firmware, which in the eHCA case is the
> > IBMEHCA> H_DEFINE_AQP1 triggered by ib_create_qp with IB_QPT_GSI
> > IBMEHCA> parameter.  AFTER that call handshaking between system
> > IBMEHCA> firmware and the SM will start, here's a new adapter
> > IBMEHCA> active on a switch port... what's your guid? here's your
> > IBMEHCA> LID, p_key, SM lid....  ...and after all that it's
> > IBMEHCA> possible to send and receive packets from the fabric.
> > IBMEHCA> The openib stack expects that a port is fully functional
> > IBMEHCA> after this create_qp returns, and starts to do all sorts
> > IBMEHCA> of modify QP and post send.  So the only choice we have
> > IBMEHCA> there is to delay create_qp until the complete
> > IBMEHCA> handshaking between system firmware and the SM has
> > IBMEHCA> finished (until we see a IB_PORT_ACTIVE in hcad_mod). If
> > IBMEHCA> we don't see that until EHCA_PORT_ACTIVE_TIMEOUT we have
> > IBMEHCA> to return an error code to openib, otherwise we're
> > IBMEHCA> seriously in trouble (tried that).
> >