lkml.org 
[lkml]   [2022]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v4 0/3] sched, cgroup/cpuset: Keep user set cpus affinity
Date
v4:
- Update patch 1 to make sched_setaffinity() the only function to
update user_cpus_ptr to make the logic simpler and
easier to understand. restrict_cpus_allowed_ptr() and
relax_compatible_cpus_allowed_ptr() will just use it if present.

v3:
- Attach a new patch 2 to introduce a copy_user_cpus_mask() to copy
out user masks with lock protection & use it in patch 3.

v2:
- Rework the v1 patch by extending the semantics of user_cpus_ptr to
store user set cpus affinity and keeping to it as much as possible.

The user_cpus_ptr field is added by commit b90ca8badbd1 ("sched:
Introduce task_struct::user_cpus_ptr to track requested affinity")
which uses it narrowly to allow keeping cpus affinity intact with
asymmetric cpu setup.

This patchset extends user_cpus_ptr to store user set cpus affinity via
sched_setaffinity() API. With that information avaiable, it will enable
cpuset to keep cpus afinity as close to what the user wants as possible
within the cpu list constraint of the current cpuset. Otherwise some
change to the cpuset hierarchy may reset the cpumask of the tasks in
the affected cpusets to the default cpuset value even if those tasks
have cpus affinity explicitly set by the users before.

It also means that once sched_setaffinity() is called, user_cpus_ptr
will remain allocated until the task exits.

Waiman Long (3):
sched: Use user_cpus_ptr for saving user provided cpumask in
sched_setaffinity()
sched: Provide copy_user_cpus_mask() to copy out user mask
cgroup/cpuset: Keep user set cpus affinity

include/linux/sched.h | 1 +
kernel/cgroup/cpuset.c | 28 +++++++++-
kernel/sched/core.c | 119 ++++++++++++++++++++++++-----------------
kernel/sched/sched.h | 1 -
4 files changed, 98 insertions(+), 51 deletions(-)

--
2.31.1

\
 
 \ /
  Last update: 2022-08-16 17:13    [W:0.049 / U:2.076 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site