From 62e05ca5edaa8e788d4d74bb72d2209cf776a1cf Mon Sep 17 00:00:00 2001 From: bergware Date: Tue, 4 Sep 2018 12:18:01 +0200 Subject: [PATCH] Added CPU isolation Both CPU pinning and CPU isolation is possible thru the GUI --- plugins/dynamix/CPUisol.page | 29 ++++++++++++++ plugins/dynamix/CPUset.page | 52 +++++++++++++++++------- plugins/dynamix/include/CPUset.php | 38 ++++++++++++++++++ plugins/dynamix/include/UpdateOne.php | 10 ++++- plugins/dynamix/include/UpdateTwo.php | 57 +++++++++++++++++++++++++++ 5 files changed, 170 insertions(+), 16 deletions(-) create mode 100644 plugins/dynamix/CPUisol.page diff --git a/plugins/dynamix/CPUisol.page b/plugins/dynamix/CPUisol.page new file mode 100644 index 000000000..5c209539b --- /dev/null +++ b/plugins/dynamix/CPUisol.page @@ -0,0 +1,29 @@ +Menu="CPUset" +Title="CPU Isolation" +Tag="leaf" +--- + +
+ + + + +
Isolation
+ +
+ +> CPU isolation allows the user to specify CPU cores that are to be explicitly reserved for assignment (to VMs or Containers). +> +> This is incredibly important for gaming VMs to run smoothly because even if you manually pin your docker containers to not overlap with your gaming VM, +> the host OS can still utilize those same cores as the guest VM needs for things like returning responses for the webGui, running a parity check, btrfs operations, etc. diff --git a/plugins/dynamix/CPUset.page b/plugins/dynamix/CPUset.page index 9176aa749..a158fcf77 100644 --- a/plugins/dynamix/CPUset.page +++ b/plugins/dynamix/CPUset.page @@ -1,8 +1,9 @@ Menu="OtherSettings" Title="CPU Pinning" +Type="xmenu" Icon="grid.png" Tag="map-marker" -Cond="pgrep('libvirtd')!==false || pgrep('dockerd')!==false" +Tabs="true" ---