>> How do you think about to delegate such an implementation detail
>> to a configurable job submission system?
>
> That could be done, but the current implementation of the jobserver
> software isn't really separable like that. It would be a nice thing to
> make a more abstract API which could b
> There are two completely separate things: one thing is make deciding
> how many jobs can be run in parallel and when more jobs can be started.
Thanks for your explanation.
> That's controlled by the jobserver and currently there's no
> way to replace the built-in jobserver implementation with
On Mon, 2015-01-05 at 18:24 +0100, SF Markus Elfring wrote:
> > Jobserver is a method of communicating how many jobs make thinks are
> > running between different instances (parent/child) of the make
> > program itself, so it knows that no more than N jobs are invoked
> > between all instances.
>
> Jobserver is a method of communicating how many jobs make thinks are
> running between different instances (parent/child) of the make
> program itself, so it knows that no more than N jobs are invoked
> between all instances.
How do you think about to delegate such an implementation detail
to a
On Sat, 2015-01-03 at 23:30 +0100, SF Markus Elfring wrote:
> There are programming interfaces available which
> provide support for submitting jobs to bigger and
> more powerful computer systems.
> I imagine that the software "jobserver" could
> be extended for the convenient reuse of such APIs.
