Re: [Scst-devel] Task managment & ordering in scst_user

[Gilad H <gil...@gm...>]

On Sun, Jun 27, 2010 at 9:20 PM, Uri Yanai <Uri...@ng...> 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)
>
> 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 ?
>
> 3.      3. What should be performed in *scst_user* when management
> functions are received, if all task sets are handled by the SCST core?
>
>       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
>
>

1) scst_user itself identifies commands using a pointer to a scst_cmd. If
you are referring to the user space application, then take a look at the
scst_user_get_cmd structure, this is the structure the user space
application gets from scst_user. The first field is cmd_h and it is used to
uniquely identify a command.


Gilad.