The attached patch introduces a mechanism for sites to allow jobs
to use specialized resources.  Jobs take advantage of this
capability by designating --core-spec=0.

in his SQUEUE_FORMAT.

the sinfo command is parallelized for performance reasons and it
really can not be completely parallelized for some use cases.
see bug 883

Correct logic to support Power7 processor with 1 or 2 threads per core
(CPU IDs are not consecutive).
bug 891

There was some logic copied from bitstring.c and an unused variable
problem reported by the compiler.

Conflicts:
	META

This is due to a bug introduced in commit 83d626ca
SOme configurations could result in NULL names in the node list table
(e.g. hidden partitions).

SLowness introduced in commit 83d626ca

This reverts commit 0d6a9965
That patch would permit a job with shared resources to run on
the same node as a job without shared resources, unfortunately
it let those jobs share CPUs. Finer grained sharing might be
possible with extensive code changes, but not something to
work on now.

Without this change, the job's --shared option when used with a partition
configuration of Shared=YES was not being honored by the select/cons_res
or select/serial plugin.

Original code was implicitly setting a job's shared field to 1
for select/cons_res.

This reverts commit c773b750

Conflicts:
	META
	NEWS

display larger sharing values.

cores specialization test 17.34 failed with bad assignment logic

including state, job ids and allocated nodes counter.