From: Vladislav B. <vs...@vl...> - 2010-06-29 13:52:39
|
Hi, Uri Yanai, on 06/27/2010 10:20 PM wrote: > Hi > > I have three questions regarding task management and ordering in the > *scst_user* handler. > > 1. When an initiator sends commands in parallel, how *scst_user* > identifies which exec belong to which command (the *sn* field in > *scst_user_scsi_cmd_parse parse_cmd *and *scst_user_scsi_cmd_exec > exec_cmd* is always zero) Gilad answered it. > 2. SCST perform *do_exec* when it’s time to execute a command, which > means that SCST controls the execution order. What is the logic when > *scst_user* defines self ordering (*has_own_order_mgmt != 0* ) ? What > is the trigger for *do_exec* in this case ? SCST is responsible for commands in-order delivery (if needed) only until exec() callback of the corresponding dev handler. If the dev handler has has_own_order_mgmt set, after that it has the full responsibility for the commands order. Otherwise, SCST will send the next command, when ordered execution is needed, only after the previous one(s) completed. See SAM for more info when ordered commands executions is needed. > 3. 3. What should be performed in *scst_user* when management > functions are received, if all task sets are handled by the SCST core? Any additional tasks you'd like to do. > Appreciate any help > > Regards > > Uri > > er > > h > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > > > ------------------------------------------------------------------------ > > _______________________________________________ > Scst-devel mailing list > Scs...@li... > https://lists.sourceforge.net/lists/listinfo/scst-devel |