Hey folks, The parallel state machine code basically works.
I have tested simple operations (ping, cp-in-cp-out, mkdir, rmdir, rm, mv) and they seem to work. I have tested a very simple parallel state machine in src/server/get-config.sm where I created a 3-state machine that prints some messages to stderr, then I modified the original SM to run 4 parallel copies of this. With this in place again the simple tests seem to work.
If you want to see what a parallel state machine looks like, take a look at this code - obviously I will need to remove it before we merge back with the main trunk.
So, what I'm not clear on at the moment is what tests we need to run before we merge with the trunk. I'm eager to do the merge before the trunk diverges much more from my branch, since I have several edits in each and every state machine file. In particular, I don't have a more sophisticated test of parallel state machine, because I'm not all THAT familliar with things that I would know what to try. My first concern has been to get the changes in but allow the existing code to work correctly, figuring that development of parallel SM code will most likely uncover some issues in their own branch.
There is also documentation. I am committed to writing up a quick state machine language programmers guide, including the new parallel state machine stuff. That will take time, of course.
So, I would appreciate some help running some tests on the branch, while I start documenting, and let me know when you think I should start merging it back with the trunk. Or I'm open to whatever other suggestions ...
Walt -- Dr. Walter B. Ligon III Associate Professor ECE Department Clemson University _______________________________________________ Pvfs2-developers mailing list Pvfs2-developers@beowulf-underground.org http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
