[ofw] initiator/target values during srp login
Leonid Keller
leonid at mellanox.co.il
Tue Jul 15 07:54:37 PDT 2008
The identifier of the port consists of two fields.
As far as guids are unique, also init_port_id and targ_port_id are
unique.
And as for using target ext_id as initiator one - why not, instead of
inventing your own one ...
> -----Original Message-----
> From: ofw-bounces at lists.openfabrics.org
> [mailto:ofw-bounces at lists.openfabrics.org] On Behalf Of chas
> williams - CONTRACTOR
> Sent: Friday, July 11, 2008 8:21 PM
> To: ofw at lists.openfabrics.org
> Subject: [ofw] initiator/target values during srp login
>
> 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?
> _______________________________________________
> ofw mailing list
> ofw at lists.openfabrics.org
> http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
>
More information about the ofw
mailing list