Hi
We’re trying to run domserver an judgedaemons on the same machine (a 6 core VM). My plan so far is to use the kernel flag isolcpus to reserve 4 cores for the judgedaemons. My question is that when we bind a judgedaemon using judgedamon -n does it set the affinity to the right mask by itself or do I need to do something?
Thanks Parth Mittal
PS. I’d also appreciate any alternate approaches that you have in mind.
On 05-06-16 15:49, Parth Mittal wrote:
Hi
We’re trying to run domserver an judgedaemons on the same machine (a 6 core VM). My plan so far is to use the kernel flag isolcpus to reserve 4 cores for the judgedaemons. My question is that when we bind a judgedaemon using judgedamon -n does it set the affinity to the right mask by itself or do I need to do something?
Yes, the argument of -n is passed on via testcasse_run.sh to runguard's -P option, which binds the process to the CPU core with that ID. So if you start 4 judgedaemons with arguments to -n the 4 cores you want to use, then there's nothing else you need to do.
The one extra thing you could do, is explicitly make other processes *not* use those 4 cores, but I'm not sure that's easy to do.
Best, Jaap
Hi Jaap
Thank you for the quick reply.
The one extra thing you could do, is explicitly make other processes *not* use those 4 cores, but I'm not sure that's easy to do.
From what I could understand about it, the isolcpus kernel argument does exactly that. It does not give the CPUs passed to it to any process which does not explicity bind itself to them.
I will implement this, and report back my findings.
Thanks Parth Mittal
-
Jaap Eldering -
Parth Mittal