Loading
test/vhost: Remove cpuset limit enforced upon vhost cpus
This limit didn't do much in a first place. It was creating separate cgroup with mem nodes already set to 0-1 nodes - in practice these are all the NUMA nodes available for mem allocation by the very default. Regarding cpus, vhost is already limited by its own cpumask's affinity hence there's no need to enforce this limit via a dedicated cgroup. Lastly, this was not taking into consideration the fact that other processes may still be scheduled on the vhost cpus as the cgroups they belong to were not modified in any way (like in case of the scheduler tests for instance). That said, the amount of jitter coming from these 3rd party processes would not have much bearing on vhost anyway - the only processes that could be more noisy are QEMU's but each VM instance is already put into a separate cgroup (see test/vhost/common.sh). Signed-off-by:Michal Berger <michal.berger@intel.com> Change-Id: I1de24bfc9e24f8f6391207e579cc599ea5c82094 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16890 Reviewed-by:
Karol Latecki <karol.latecki@intel.com> Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com>