[Pvfs2-developers] purpose for nested state machines in prelude.sm

[Sam Lang]

Hi Elaine,

Yeah, I want those separate.  The inode stuffing changes that Phil and  
I made take advantage of the prelude_work sm.  You can look at the  
batch-remove state machine in the small-file-branch for an example.   
The prelude state machine assumes that a server operation is being  
done on only one object (fsid, handle), where in some cases we may  
have a server request with an array of objects.

-sam

On Sep 2, 2008, at 3:04 PM, Elaine Quarles wrote:

> The file prelude.sm contains two state machines. They are  
> pvfs2_prelude_work_sm and pvfs2_prelude_sm.
>
> From what I can see, pvfs2_prelude_work_sm is only started from  
> within pvfs2_prelude_sm. All other state machines jump to  
> pvfs2_prelude_sm. Does anyone know of a reason why these cannot be  
> combined into one state machine?
>
> Thanks
> Elaine Quarles
> _______________________________________________
> Pvfs2-developers mailing list
> Pvfs2-developers at beowulf-underground.org
> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.beowulf-underground.org/pipermail/pvfs2-developers/attachments/20080902/09d70534/attachment.htm