Vladislav Bolkhovitin wrote:
Vu Pham wrote:
3) This may not be the forum for this, but how can you terminate a
session using SCST proc commands?
SCST can't (and shouldn't) do that, because it has no knowledge about
how sessions with particular target transport created and destroyed.
Sessions management is the target driver's duty. Ask Vu that feature.
Normally {srp connection, scst session} will be destroyed upon
disconnect reques or new connection request (without multi-channels
flag) coming from initiator or QP is in error condition.
Sometimes we fail to terminate scst session when there are outstanding
I/Os on scst session which does not match the outstanding I/Os on the
srp connection. Right after srp calls scst_init_cmd_done, it increases
the active command counter and decreases the counter on on_free_command.
Any idea Vlad?
Sorry, I don't understand, what's the problem with them?
I keep track of the number of outstanding scst_cmnd on a
{srp connection, scst session} and it does not match with
scst_sess->refcnt - or it should be off by 1; however, it
does not. Therefore scst_unregister_session (wait 1) stuck
most of the time.
-vu
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
