public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Xuewen Yan <xuewen.yan94@gmail.com>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Juri Lelli" <juri.lelli@redhat.com>,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Benjamin Segall" <bsegall@google.com>,
	"Mel Gorman" <mgorman@suse.de>,
	"Valentin Schneider" <vschneid@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"王科 (Ke Wang)" <Ke.Wang@unisoc.com>,
	"Xuewen Yan" <xuewen.yan@unisoc.com>,
	"hongyu.jin@unisoc.com" <hongyu.jin@unisoc.com>,
	guohua.yan@unisoc.com, "John Stultz" <jstultz@google.com>
Subject: Re: [Question] Sched: Severe scheduling latency (>10s) observed on kernel 6.12 with specific workload
Date: Wed, 8 Apr 2026 13:19:30 +0100	[thread overview]
Message-ID: <20260408131930.28c1e80a@pumpkin> (raw)
In-Reply-To: <CAB8ipk9N5_pO1Awp6PLnWt6hf1Bu_XtY3qGMJKqz=Uf6eZQejw@mail.gmail.com>

On Wed, 1 Apr 2026 10:32:30 +0800
Xuewen Yan <xuewen.yan94@gmail.com> wrote:

> Dear Linux maintainers and reviewers,
> 
> I am writing to report a severe scheduling latency issue we recently
> discovered on Linux Kernel 6.12.
> 
> Issue Description
> 
> We observed that when running a specific background workload pattern,
> certain tasks experience excessive scheduling latency. The delay from
> the runnable state to running on the CPU exceeds 10 seconds, and in
> extreme cases, it reaches up to 100 seconds.

Have you managed to get a low priority process spinning in kernel on the
cpu the RT process last ran on?
The RT process will always run on the same cpu it ran on provided in
is higher priority than the current process running on that cpu.

ftrace logging scheduler events is you 'friend' here.

	David 

> 
> Environment Details
> 
> Kernel Version: 6.12.58-android16-6-g3835fd28159d-ab000018-4k
> Architecture: [ ARM64]
> Hardware: T7300
> Config: gki_defconfig
> 
> RT-app‘s workload Pattern:
> 
> {
>     "tasks" : {
>             "t0" : {
>                     "instance" : 40,
>                     "priority" : 0,
>                     "cpus" : [ 0, 1, 2, 3 ],
> "taskgroup" : "/background",
>                     "loop" : -1,
>                     "run" : 200,
>                     "sleep" : 50
>             }
>     }
> }
> 
> And we have applied the following patchs:
> 
> https://lore.kernel.org/all/20251216111321.966709786@linuxfoundation.org/
> https://lore.kernel.org/all/20260106170509.413636243@linuxfoundation.org/
> https://lore.kernel.org/all/20260323134533.805879358@linuxfoundation.org/
> 
> 
> Could you please advise if there are known changes in the eevdf in
> 6.12 that might affect this specific workload pattern?
> 
> Thanks!
> 
> BR
> ---
> xuewen


      parent reply	other threads:[~2026-04-08 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAB8ipk9N5_pO1Awp6PLnWt6hf1Bu_XtY3qGMJKqz=Uf6eZQejw@mail.gmail.com>
2026-04-01  4:25 ` [Question] Sched: Severe scheduling latency (>10s) observed on kernel 6.12 with specific workload John Stultz
2026-04-01  6:04   ` Xuewen Yan
2026-04-01 10:05     ` Vincent Guittot
2026-04-01 10:48       ` Xuewen Yan
2026-04-01 13:00         ` Dietmar Eggemann
2026-04-02  5:16           ` Xuewen Yan
2026-04-02 14:58             ` Dietmar Eggemann
2026-04-08  2:50               ` Xuewen Yan
2026-04-01 14:01         ` Vincent Guittot
2026-04-02  5:11           ` Xuewen Yan
2026-04-02  5:24             ` Xuewen Yan
2026-04-08 12:19 ` David Laight [this message]

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=20260408131930.28c1e80a@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=Ke.Wang@unisoc.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=guohua.yan@unisoc.com \
    --cc=hongyu.jin@unisoc.com \
    --cc=jstultz@google.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=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