On Wednesday 06 June 2007 12:03, Greg Ercolano wrote:
> [posted to rush.general]
>
> Antoine Durr wrote:
> > Well, the problem with changing the # of cpus allocated to a job is
> > that you stomp on information that could be critical to the job, e.g.
>
> I see; one way to communicate that to the watcher would be to
> have the job specify 'maxcpus 4' (rush submit command), and the
> watcher could notice that and honor it as a 'given limit' for
> that particular job, and not assign more cpus than that.
In our system we communicate scheduling information like this using the
"Notes" field of the job submission. In fact from Gregs docs "Each job has a
free form 'notes' field, which can be used for various purposes, such as
passing informational notes to other programs..."
|