From: Tim Chen <tim.c.chen@linux.intel.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>, linux-kernel@vger.kernel.org
Cc: 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,
bristot@redhat.com, vschneid@redhat.com, gautham.shenoy@amd.com
Subject: Re: [PATCH] sched/fair: Skip newidle_balance() when an idle CPU is woken up to process an IPI
Date: Mon, 22 Jan 2024 13:59:14 -0800 [thread overview]
Message-ID: <b4f5ac150685456cf45a342e3bb1f28cdd557a53.camel@linux.intel.com> (raw)
In-Reply-To: <20240119084548.2788-1-kprateek.nayak@amd.com>
On Fri, 2024-01-19 at 14:15 +0530, K Prateek Nayak wrote:
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index b803030c3a03..1fedc7e29c98 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -8499,6 +8499,16 @@ done: __maybe_unused;
> if (!rf)
> return NULL;
>
> + /*
> + * An idle CPU in TIF_POLLING mode might end up here after processing
> + * an IPI when the sender sets the TIF_NEED_RESCHED bit and avoids
> + * sending an actual IPI. In such cases, where an idle CPU was woken
> + * up only to process an interrupt, without necessarily queuing a task
> + * on it, skip newidle_balance() to facilitate faster idle re-entry.
> + */
> + if (prev == rq->idle)
> + return NULL;
> +
Should we check the call function queue directly to detect that there is
an IPI waiting to be processed? something like
if (!llist_empty(&per_cpu(call_single_queue, rq->cpu)))
return NULL;
Could there be cases where we want to do idle balance in this code path?
Say a cpu is idle and a scheduling tick came in, we may try
to look for something to run on the idle cpu. Seems like after
your change above, that would be skipped.
Tim
> new_tasks = newidle_balance(rq, rf);
>
> /*
next prev parent reply other threads:[~2024-01-22 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 8:45 K Prateek Nayak
2024-01-22 21:59 ` Tim Chen [this message]
2024-01-23 4:58 ` K Prateek Nayak
2024-01-23 8:06 ` Vincent Guittot
2024-01-23 10:00 ` K Prateek Nayak
2024-01-23 13:39 ` Vincent Guittot
2024-01-24 8:26 ` K Prateek Nayak
2024-01-23 21:17 ` David Vernet
2024-01-24 8:35 ` K Prateek Nayak
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=b4f5ac150685456cf45a342e3bb1f28cdd557a53.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gautham.shenoy@amd.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.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 \
/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®