Hi,
Maybe you remember my old email where I talked about the visualization 
environment? Maybe I should have sent it to the developers list instead of 
the internal list :-)
Well, I thought it is nice to visualize the state transitions with jumpshot, 
e.g. create a event for each new state. In order to nicely display the name 
of the state and the statemachines name I thought of a external mapping file.
However, therefore it would be great to have a unique id for each statemachine 
and for each state with an a sm. I think it could be handy to have such IDs 
for other tasks as well, for example to generate the array of available SMs 
automatically ...
I implemented the unique IDs for my own migration-hint branch and the sm 
parser. Just to figure out that you changed the sm parser recently :-)
For the unique SM ID the makefile just ran a find of the sms and the line 
number in the resulting file is the unique ID. This number then gets assigned 
by the sm compiler to a new field. Right now I will not update to the new CVS 
version, so I won't implement it for it. Especially because I don't know if 
you'll find it handy.
With this email I just want to inform you about the work I do and hope to 
discuss about the unique ids for the statemachines and their states and that 
these might be useful for various things. Maybe I will post links to some  
slog2 logs which contain these IDs if you are interested. In my opininion it 
is nice to see all the server activity and be able to associate them with the 
state which triggered them.

Best regards,
Julian
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers

Reply via email to