MAX_JOBS_PREF and MAX_CPUS_PREF not behaving as expect.

[lfield]

This is related to the MAX_JOBS_PREF and MAX_CPUS_PREF project preferences as added in this commit.

The current the behavior for a multi-threaded application is as follows (threads are cpus for the VM apps):

Max 1 CPU, Max 1 Job  = >  1 single threaded job
Max 2 CPU, Max 1 Job => 2 threaded job 
Max 1 CPU, Max 2 Job  => 1 single threaded job
Max 2 CPU, Max 2 Job => 2 x 2 threaded jobs

In practice Max CPUs is used to set the number of threads and hence CPUs to be used by a VM, hence Max 1 CPU, Max 2 Job => 1 single threaded job does not function as wished. In this case it should run two single CPU jobs.

[lfield]

Removing this if statement partially resolves the issue, however the Max # CPU preference cannot be used to limit the number CPUs used by the VM. This means the VM will have the maximum number of CPUs given by g_wreq->effective_ncpus.

[lfield]

The number of CPUs used by a VM can be controlled if the if statement from sched_send is added to plan_class.cpp after the max_threads check. The remaining issue is that in one request if 3 ncpus are available and max_cpu = 2, two 2 CPU jobs are returned where as it should be one 2 CPU and one 1 CPU. If the requests are made separately the correct response is given.