I do believe that it works as described in the comments, although it hasn't been tested in a while so verify that it works as desired. It was added after the original code as developed, which is why both CR_SOCKET and CR_CORE are set (it accomplishes the desired functionality with minimal code changes).
#if(0) /* Using CR_SOCKET or CR_SOCKET_MEMORY will not allocate a socket to more * than one job at a time, but it also will not grant a job access to more * CPUs on the socket than requested. If ALLOCATE_FULL_SOCKET is defined, * then a job will be given access to every cores on each allocated socket. */ #define ALLOCATE_FULL_SOCKET 1 #endif Quoting Michel Bourget <[email protected]>: > Hi, > > given the description in the source, I am considering enabling this > feature. But it seems incomplete. Am i missing something ? What > puzzles me is CR_SOCKET and CR_CORE seems to be "equal" when > ALLOCATE_FULL_SOCKET > is disabled. What is the rationale there ? A todo ? > > Tia > > -- > > ----------------------------------------------------------- > Michel Bourget - SGI - Linux Software Engineering > "Past BIOS POST, everything else is extra" (travis) > ----------------------------------------------------------- > >
