From: Peter Zijlstra <peterz@infradead.org>
To: Li kunyu <likunyu@open-hieco.net>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, kprateek.nayak@amd.com,
linux-kernel@vger.kernel.org,
"Li Wang (Hieco)" <li.wang@linux.dev>
Subject: Re: [RFC PATCH 1/6] sched/fair: Add SMT sibling push in periodic load balance
Date: Wed, 21 Oct 2026 14:34:38 +0200 [thread overview]
Message-ID: <20261021123438.GG2823843@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20261020083746.37068-2-likunyu@open-hieco.net>
On Tue, Oct 20, 2026 at 04:37:41PM +0800, Li kunyu wrote:
Just a few remarks on coding style while I try and make sense of the
whole thing. Don't go rush out a new version with this stuff fixed
before you've seen feedback on the higher level stuff.
> @@ -14226,6 +14244,94 @@ update_newidle_cost(struct sched_domain *sd, u64 cost, unsigned int success)
> return false;
> }
>
> +/*
> + * An exciting thing is that we have implemented an efficient push
> + * function process.
> + *
> + * It is applied in cycle load balancing and nohz_kick process.
> + * It can help us solve the problem of high workload of CFS tasks in
> + * the RQ queue.
> + */
> +static bool smt_buddy_move_task(struct rq *src_rq)
> +{
> + bool is_overload, is_move = false;
> + int src_cpu = cpu_of(src_rq), smt_cpu;
> + unsigned long src_cpu_runnable, smt_cpu_runnable;
> + struct sched_domain *smt_sd;
> + struct task_struct *p;
> + struct rq *smt_rq;
> + struct rq_flags rf;
> +
> + if (!sched_feat(SMT_BUDDY_ASSIST) || !sched_smt_active())
> + goto exit;
> +
> +restart:
> + if (src_rq->nr_running < 2)
> + goto exit;
Did this want to be:
while (src_rq->nr_running > 1) {
> +
> + rcu_read_lock();
scoped_guard (rcu) {
> +
> + is_overload = false;
> + src_cpu_runnable = cpu_runnable(src_rq);
> + for_each_cpu(smt_cpu, cpu_smt_mask(src_cpu)) {
> + if (smt_cpu == src_cpu)
> + continue;
> +
> + smt_cpu_runnable = cpu_runnable(cpu_rq(smt_cpu));
> + if ((src_cpu_runnable * 100 > smt_cpu_runnable * sysctl_smt_buddy_imbalance_pct)
> + && cpu_active(smt_cpu)) {
This is horrifically bad indenting. Operators go at the end of the
previous line and then you indent to the level of whatever ( is active.
If you're a vim user 'cino=(0' gets you that.
> + is_overload = true;
> + break;
> + }
> + }
> +
> + if (!is_overload) {
> + rcu_read_unlock();
> + goto exit;
This pattern should scream at you for doing it wrong.
> + }
> +
> + smt_sd = lowest_flag_domain(src_cpu, SD_SHARE_CPUCAPACITY);
> + if (!smt_sd) {
> + rcu_read_unlock();
> + goto exit;
And again.
> + }
> +
> + rcu_read_unlock();
}
> +
> + rq_lock_irqsave(src_rq, &rf);
scoped_guard (irqsave) {
scoped_guard (rq_lock, src_rq)
> + smt_rq = cpu_rq(smt_cpu);
> +
> + struct lb_env env = {
> + .sd = smt_sd,
> + .dst_cpu = smt_cpu,
> + .dst_rq = smt_rq,
> + .src_cpu = src_cpu,
> + .src_rq = src_rq,
> + .idle = 0, /* __CPU_NOT_IDLE */
> + .flags = LBF_ACTIVE_LB,
> + };
> +
> + /* Update the src_rq clock only once when migrating tasks. */
> + if (!is_move)
> + update_rq_clock(src_rq);
> +
> + p = detach_one_task(&env);
> + if (!p) {
> + rq_unlock_irqrestore(src_rq, &rf);
> + goto exit;
More of the same bad pattern.
> + }
> +
> + rq_unlock(src_rq, &rf);
}
> + attach_one_task(smt_rq, p);
> + local_irq_restore(rf.flags);
}
> + is_move = true;
> +
> + goto restart;
}
> +
> +exit:
> + return is_move;
> +}
next prev parent reply other threads:[~2026-10-21 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 8:37 [RFC PATCH 0/6] sched/fair: Introduce the SMT_BUDDY_ASSIST feature Li kunyu
2026-10-20 8:37 ` [RFC PATCH 1/6] sched/fair: Add SMT sibling push in periodic load balance Li kunyu
2026-10-21 12:34 ` Peter Zijlstra [this message]
2026-10-20 8:37 ` [RFC PATCH 2/6] sched/fair: Add is_smt_buddy_run() to skip SMT domain Li kunyu
2026-10-21 12:35 ` Peter Zijlstra
2026-10-20 8:37 ` [RFC PATCH 3/6] sched/fair: SMT sibling exclusion after successful push Li kunyu
2026-10-21 12:39 ` Peter Zijlstra
2026-10-20 8:37 ` [RFC PATCH 4/6] sched/fair: Restrict newidle balance to LLC domain Li kunyu
2026-10-21 12:42 ` Peter Zijlstra
2026-10-20 8:37 ` [RFC PATCH 5/6] sched/fair: Add task burst threshold for large-scale bursts Li kunyu
2026-10-21 12:54 ` Peter Zijlstra
2026-10-20 8:37 ` [RFC PATCH 6/6] sched/docs: Add documentation for SMT Buddy Assist feature Li kunyu
2026-10-21 12:55 ` Peter Zijlstra
2026-10-21 12:44 ` [RFC PATCH 0/6] sched/fair: Introduce the SMT_BUDDY_ASSIST feature Kayra Cizmeci
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=20261021123438.GG2823843@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=li.wang@linux.dev \
--cc=likunyu@open-hieco.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.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®