[ofw] initiator/target values during srp login
chas williams - CONTRACTOR
chas at cmf.nrl.navy.mil
Fri Jul 11 10:21:07 PDT 2008
i see that the srp driver currently does:
ib_api_status_t
srp_init_connection(
IN OUT srp_connection_t *p_connection,
IN ib_ioc_profile_t* const p_profile,
IN net64_t ca_guid,
IN net64_t ext_id,
IN ib_path_rec_t *p_path_rec,
IN ib_net64_t service_id )
{
...
p_connection->p_path_rec = p_path_rec;
switch( p_profile->io_class )
{
case SRP_IO_CLASS_R10:
p_connection->init_port_id.field1 = ca_guid;
p_connection->init_port_id.field2 = ext_id;
p_connection->targ_port_id.field1 = p_profile->ioc_guid;
p_connection->targ_port_id.field2 = ext_id;
break;
case SRP_IO_CLASS:
p_connection->init_port_id.field1 = ext_id;
p_connection->init_port_id.field2 = ca_guid;
p_connection->targ_port_id.field1 = ext_id;
p_connection->targ_port_id.field2 = p_profile->ioc_guid;
isnt it a bit strange to login identifying yourself as the target of the
login request? i.e. use use of ext_id for both the initiator and target?
More information about the ofw
mailing list