Hello,

I'd like to inform all the SCST target drivers developers and interested 
people that with the merged of Persistent Reservations some external 
SCST interfaces have been changed:

1. get_initiator_port_transport_id() callback added to struct 
scst_tgt_template. This callback should return the initiator's port 
TransportID in the format defined by SPC for your transport. It is 
necessary for the Persistent Reservation. This callback is optional, but 
without it for initiators of your target driver Persistent Reservation 
commands would not be accessible and look as not supported. It is very 
simple to implement this callback: in most cases you should just copy as 
is initiator (port) name from the session creation packet your hardware 
delivered to your driver. You can find full description of 
get_initiator_port_transport_id() callback in comments for it in scst.h.

2. In function scst_register_session() added one more parameter "void 
*tgt_priv". It is necessary, because SCST session initialization code 
can call get_initiator_port_transport_id() callback before 
scst_register_session() returned and you may need tgt_priv inside 
get_initiator_port_transport_id(). Correspondingly, the following after 
scst_register_session() scst_sess_set_tgt_priv() call isn't needed 
anymore. All the target drivers in the SCST SVN updated for this change.

3. Functions scst_register() and scst_unregister() renamed to 
scst_register_target() and scst_unregister_target() correspondingly to 
better reflect their goals. All the target drivers in the SCST SVN 
updated for this change.

Also, I'd like to remind, that if you not updated your target driver for 
the sysfs interface yet, it's time to do it. The update isn't required 
(everything will work without it), but it is highly desired for every 
target driver to support "enabled" attribute to prevent its users from 
nasty surprises when initiators for it loaded before it finished 
initialization.

Vlad
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel

Reply via email to