mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Huang Shijie <shijie@os.amperecomputing.com>
To: mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org
Cc: patches@amperecomputing.com, cl@linux.com,
	Shubhang@os.amperecomputing.com, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	linux-kernel@vger.kernel.org, vschneid@redhat.com,
	vineethr@linux.ibm.com, kprateek.nayak@amd.com,
	Huang Shijie <shijie@os.amperecomputing.com>
Subject: [PATCH v6 0/2] sched: update the rq->avg_idle when a task is moved to an idle CPU
Date: Tue,  9 Dec 2025 17:45:06 +0800	[thread overview]
Message-ID: <20251209094508.570049-1-shijie@os.amperecomputing.com> (raw)

In the newidle balance, the rq->idle_stamp may set to a non-zero value
if it cannot pull any task.

In the wakeup, it will detect the rq->idle_stamp, and updates
the rq->avg_idle, then ends the CPU idle status by setting rq->idle_stamp
to zero.

Besides the wakeup, current code does not end the CPU idle status
when a task is moved to the idle CPU, such as fork/clone, execve,
or other cases.

This patch set tries to resolve it.

Tested this patch set with Specjbb:
   There is no regression for this patch set

v5--> v6:
    Remove "this_rq->idle_stamp = 0;" in patch 1.
    Update the test result with Specjbb.
   --v5:https://lkml.org/lkml/2025/12/3/179

v4--> v5:
    Modify the changelog.

   --v4:https://lkml.org/lkml/2025/11/28/300

v3--> v4:
     Remove the code for delayed task.

   --v3: https://lkml.org/lkml/2025/11/27/456

v2--> v3:
  -- merge patch 3 into patch 2:
      move update_rq_avg_idle() to enqueue_task().

   --v2: https://lkml.org/lkml/2025/11/27/214   

v1--> v2:
  -- Put update_rq_avg_idle() to activate_task()
  -- Add Delay-dequeue task check.	

   --v1: https://lkml.org/lkml/2025/11/24/97

Huang Shijie (2):
  sched/fair: set rq->idle_stamp at the end of the sched_balance_newidle
  sched: update the rq->avg_idle when a task is moved to an idle CPU

 kernel/sched/core.c | 29 +++++++++++++++++------------
 kernel/sched/fair.c | 10 ++++++----
 2 files changed, 23 insertions(+), 16 deletions(-)

-- 
2.40.1


             reply	other threads:[~2025-12-09  9:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09  9:45 Huang Shijie [this message]
2025-12-09  9:45 ` [PATCH v6 1/2] sched/fair: set rq->idle_stamp at the end of the sched_balance_newidle Huang Shijie
2025-12-09  9:45 ` [PATCH v6 2/2] sched: update the rq->avg_idle when a task is moved to an idle CPU Huang Shijie
2025-12-11 16:15   ` Dietmar Eggemann
2025-12-12  3:16     ` Shijie Huang
2025-12-12 14:22       ` Dietmar Eggemann
2025-12-15  9:35         ` Shijie Huang
2025-12-17 16:15           ` Dietmar Eggemann
2026-01-07 15:48             ` Dietmar Eggemann
2026-01-09 13:33               ` Vincent Guittot
2025-12-13  1:36   ` Vincent Guittot
2025-12-16  6:22     ` Shijie Huang
2025-12-16  7:17       ` Vincent Guittot
2025-12-16  7:38         ` Shijie Huang
2025-12-16  8:47           ` Vincent Guittot
2025-12-16  9:49             ` Shijie Huang

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=20251209094508.570049-1-shijie@os.amperecomputing.com \
    --to=shijie@os.amperecomputing.com \
    --cc=Shubhang@os.amperecomputing.com \
    --cc=bsegall@google.com \
    --cc=cl@linux.com \
    --cc=dietmar.eggemann@arm.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=patches@amperecomputing.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vineethr@linux.ibm.com \
    --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®