This needs a lot of work, but checking in the framework for now.

wait for.

based on the mask given.

task/affinity.

thread in a core.

it can bind cyclically across sockets.

0c090f95

add a PriorityFlags option of CALCULATE_RUNNING. If set, then the
priority of running jobs will continue to be recalculated
periodically. The PriorityFlags value reported by sview and
"scontrol show config" will be reported as a string rather
than its numeric value.

Previous logic assumed cpus_per_task=1, so ntasks_per_core option
could spread the job across more cores than desired

cpus-per-task support: Try to pack all CPUs of each tasks onto one socket.
Previous logic could spread the tasks CPUs across multiple sockets.

Previous logic was counting CPUs, but assuming each task would
only use one CPU.

This reverts commit b22268d8.

Conflicts:
	src/slurmctld/job_mgr.c

Properly enforce job --requeue and --norequeue options. Previous
logic was in three places not doing so (either ignoring the value,
ANDing it with the JobRequeue configuration option or using the
JobRequeue configuration option by itself).
bug 821

Add support for a job step's CPU governor and/or frequency to be reset on
suspend/resume (or gang scheduling). The default for an idle CPU will now
be "ondemand" rather than "userspace" with the lowest frequency (to recover
from hard slurmd failures and support gang scheduling).

There should be no change in behavior with the production code,
but this will improve the robustness of the code if someone makes
changes to the logic.

Always set to default values if no user input
This is needed to clear any vestigial values from abnormal Slurm
termination.

Used uninitialized variable in using the srun --cpu-freq option to
set the CPU governor, resulting in invalid memory reference.
Some minor cosmtic changes too.

Add srun --cpu-freq options to set the CPU governor (OnDemand, Performance,
Conservative, PowerSave or UserSpace).
task/affinity: support set cpu_freq without cpuset (using hwloc and sched functions)
Fix calculation used to set --cpu-freq=highm1 (relied upon ordering of possible
CPU frequencies).

The suspend/resume is performed on a per-job basis, but the cpu_freq
is set on a per job step basis. This is a partial reversion of
commit 5e40f627

Add SelectTypeParameters option of CR_PACK_NODES to pack a job's tasks
tightly on its allocated nodes rather than distributing them evenly across
the allocated nodes.
bug 819

Job allocaitons with core specialization are allocated all available
CPUs on the selected nodes rather than only the number required to
satisfy their allocation request (e.g. "srun --core-spec=1 -n1 date"
will not be allocated 1 CPU, but will get the entire node except
for one specialized core).

something you also get a signal which would produce deadlock.

Fix Bug 601.

If a job step reqeusts specific cores outside of their allocation
with the --core-spec option, then bind the tasks to only those
CPUs available to the job.