From eb9a1f15c311e36d0afcc94d9cd0f4e4a066c225 Mon Sep 17 00:00:00 2001
From: Vladislav Bolkhovitin
Date: Thu, 6 Aug 2009 11:49:05 +0000
Subject: [PATCH] Web updates
git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@1018 d57e44dd-8a1f-0410-8b47-8ef2f437770f
---
www/contributing.html | 22 ----------------------
1 file changed, 22 deletions(-)
diff --git a/www/contributing.html b/www/contributing.html
index b8133d4e2..c34b85e3e 100644
--- a/www/contributing.html
+++ b/www/contributing.html
@@ -115,28 +115,6 @@
devices only and reject PERSISTENT RESERVE IN and OUT commands for
pass-through devices with "COMMAND NOT SUPPORTED" sense data.
- Automatic sessions reassignment
-
- At the moment, if security name for an initiator reassigned (moved) to another security
- group, the existing sessions from that initiator are not automatically reassigned to
- the new security group, i.e. they remain in the old one. The only ways to reassign them
- are either sessions restart, or restart of the corresponding target driver. Both in many
- cases are not options.
-
- To implement that you should on event of any group change:
-
- - Globally suspend all activities by scst_suspend_activity().
-
- - Go over all existing sessions. For each find the corresponding ACG
- (see scst_init_session() as an example) and check if it's the same as the existing
- one. If it's the same, then go to the next session. Otherwise, reassign
- it to the new ACG. For that you should go over all devices in the group/session
- pair (tgt_dev's) and delete not existing in the new ACG tgt_dev's,
- add new ones and keep the existing ones.
-
- - Resume the activities.
-
-
Dynamic I/O flow control
At the moment, if an initiator or several initiators simultaneously send to