From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Zhongqiu Han <quic_zhonhan@quicinc.com>, <mingo@redhat.com>,
<peterz@infradead.org>, <juri.lelli@redhat.com>,
<vincent.guittot@linaro.org>, <dietmar.eggemann@arm.com>,
<rostedt@goodmis.org>, <bsegall@google.com>, <mgorman@suse.de>,
<vschneid@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Combine ENQUEUE_MIGRATED check in activate_task()
Date: Fri, 25 Jul 2025 12:44:32 +0530 [thread overview]
Message-ID: <c7f2c6cd-e8d9-4dcc-9d1a-0a8b73769942@amd.com> (raw)
In-Reply-To: <20250724121258.1826487-1-quic_zhonhan@quicinc.com>
Hello Zhongqiu,
On 7/24/2025 5:42 PM, Zhongqiu Han wrote:
> Combine the task_on_rq_migrating() check and the sched_mm_cid_migrate_to()
> invocation into a single conditional block. This removes a redundant flag
> check and slightly reduces the instruction count in a hot path.
>
> Signed-off-by: Zhongqiu Han <quic_zhonhan@quicinc.com>
> ---
> - This is a slight optimization and code cleanup, please let me know if you'd prefer to keep the current structure.
> - Thanks
>
> kernel/sched/core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 2343f5691c54..d6063cf503ee 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -2118,10 +2118,10 @@ inline bool dequeue_task(struct rq *rq, struct task_struct *p, int flags)
>
> void activate_task(struct rq *rq, struct task_struct *p, int flags)
> {
> - if (task_on_rq_migrating(p))
> + if (task_on_rq_migrating(p)) {
> flags |= ENQUEUE_MIGRATED;
> - if (flags & ENQUEUE_MIGRATED)
I think "ENQUEUE_MIGRATED" can be individually set without
task_on_rq_migrating() in the wakeup path via ttwu_do_activate().
In that case "p->on_rq", goes from "0" to "TASK_ON_RQ_QUEUED" directly
without going through an intermediate "TASK_ON_RQ_MIGRATING" but
"ENQUEUE_MIGRATED" will be set if "p->task_cpu" was changed during
wakeup.
--
Thanks and Regards,
Prateek
> sched_mm_cid_migrate_to(rq, p);
> + }
>
> enqueue_task(rq, p, flags);
>
next prev parent reply other threads:[~2025-07-25 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 12:12 Zhongqiu Han
2025-07-25 7:14 ` K Prateek Nayak [this message]
2025-07-28 9:44 ` Zhongqiu Han
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=c7f2c6cd-e8d9-4dcc-9d1a-0a8b73769942@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quic_zhonhan@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®