[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] ASSIGN_CPU_AFFINITY - does it fence off a CPU? If not, is there a way to do so?

On 12/15/2016 04:14 PM, Michael Pelletier wrote:

Hi folks,


I’m interested in insuring that an HTCondor job running on Linux can be assigned to a specific CPU in such a way that it gets it all to itself, and no other processes are allowed to run on that CPU even if the job isn’t making use of the processor at that moment.


I’m aware of ASSIGN_CPU_AFFINITY but from the documentation it appears that it works the other way around, such that the job can only use that CPU but other jobs might still be assigned to it.


Any suggestions? The idea is to protect the HTCondor tasks from other users of the system who haven’t yet been migrated to submit their work via HTCondor, that being a work in progress. Thanks!


Depending on how the other processes are being started, can you use taskset(1) on their parent, to wall them off to some number of cores, and give condor the remaining ones?