5d49965bb9
Upon removal, there's a small chance that new threads would jump into these cgroups AFTER we read the list of PIDs to migrate. In such a case, there may be some processes left preventing us from finally removing the cgroup. Since we can't fully control that without continuously reading the list, simply ignore it. Fixes issue #2298 Signed-off-by: Michal Berger <michalx.berger@intel.com> Change-Id: I0d50b975742a8b15edd25c6b4e51ab337b017eaa Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/10872 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> |
||
---|---|---|
.. | ||
cgroups.sh | ||
common.sh | ||
governor.sh | ||
idle.sh | ||
interrupt.sh | ||
isolate_cores.sh | ||
load_balancing.sh | ||
rdmsr.pl | ||
scheduler.sh |