Timeline for CPU reservation and affinity using taskset and isolcpus kernel parameter with JVM?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 27, 2018 at 9:58 | comment | added | danidar | I read on xmodulo that the kernel parameter "isolcpus=<CPU_ID>" to the boot loader during boot or GRUB configuration file. Then the Linux scheduler will not schedule any regular process on the reserved CPU core(s), unless specifically requested with taskset. For example, to reserve CPU cores 0 and 1, add "isolcpus=0,1" kernel parameter. Upon boot, then use taskset to safely assign the reserved CPU cores to your program. | |
| Jul 27, 2018 at 8:56 | history | edited | slm♦ | CC BY-SA 4.0 |
added 237 characters in body
|
| Jul 27, 2018 at 8:54 | comment | added | slm♦ | It's possible using cgroups - unix.stackexchange.com/questions/247209/…. But not in the way you imagine. | |
| Jul 27, 2018 at 8:49 | comment | added | danidar | Is it therefore not possible to reserve cpu exclusivly to some applications and nothing else uses these cpu? | |
| Jul 27, 2018 at 2:37 | history | edited | slm♦ | CC BY-SA 4.0 |
added 143 characters in body
|
| Jul 27, 2018 at 2:32 | history | answered | slm♦ | CC BY-SA 4.0 |