From: Waiman Long <longman@redhat.com>
To: Xuewen Yan <xuewen.yan@unisoc.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
di.shen@unisoc.com, xuewen.yan94@gmail.com
Subject: Re: [RFC PATCH] sched: Do not copy user_cpus_ptr when parent is reset_on_fork
Date: Thu, 5 Sep 2024 08:42:33 -0400 [thread overview]
Message-ID: <a645086d-bffb-41b0-bd70-1ef5edb128f9@redhat.com> (raw)
In-Reply-To: <20240905090458.1173-1-xuewen.yan@unisoc.com>
On 9/5/24 05:04, Xuewen Yan wrote:
> Now, the task's user_cpus_ptr would dup from parent's user_cpus_ptr.
> It is better reset the user_cpus_ptr when parent's reset_on_fork
> is set.
According to sched(7):
Each thread has a reset-on-fork scheduling flag. When this flag
is set, children created by fork(2) do not inherit privileged
scheduling policies.
It can be argued what are considered privileged scheduling policies.
AFAICS, a restricted affinity doesn't seem to be a "privileged"
scheduling policy. That is my own opinion strictly from the definition
point of view, I will let others weigh in on that and I am OK to go
either way.
Cheers,
Longman
>
> Signed-off-by: Xuewen Yan <xuewen.yan@unisoc.com>
> ---
> kernel/sched/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index f3951e4a55e5..2fbae00cd1dc 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2666,7 +2666,7 @@ int dup_user_cpus_ptr(struct task_struct *dst, struct task_struct *src,
> * do_set_cpus_allowed().
> */
> raw_spin_lock_irqsave(&src->pi_lock, flags);
> - if (src->user_cpus_ptr) {
> + if (src->user_cpus_ptr && !src->sched_reset_on_fork) {
> swap(dst->user_cpus_ptr, user_mask);
> cpumask_copy(dst->user_cpus_ptr, src->user_cpus_ptr);
> }
next prev parent reply other threads:[~2024-09-05 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 9:04 Xuewen Yan
2024-09-05 12:42 ` Waiman Long [this message]
2024-09-05 13:12 ` Phil Auld
2024-09-05 14:00 ` Waiman Long
2024-09-05 14:09 ` Phil Auld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a645086d-bffb-41b0-bd70-1ef5edb128f9@redhat.com \
--to=longman@redhat.com \
--cc=bsegall@google.com \
--cc=di.shen@unisoc.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=ke.wang@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®