I need a crash course in the job interface.
I need to add something a lot like the scheduler but without any intelligence. Basically I'd like a SM to be able to post a job which will never have immediate completion. Then later another SM posts a release that lets the first job go. It looks like the stuff that already exists for the scheduler is pretty close to what I want, except I don't want any of the scheduler bits. What isn't clear to me is how a job moves to the completed list, or how I can maintain a list of waiting jobs and look those up. It appears some of that is going on in the calls in job.c but I don't know what's being done by the job layer and what is being done by the scheduler.
If someone who knows this stuff can email me so I can get a few questions answered then I can forge ahead myself.
Thanks! Walt -- Dr. Walter B. Ligon III Associate Professor ECE Department Clemson University _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
