From: Peter Zijlstra <peterz@infradead.org>
To: Qais Yousef <qyousef@layalina.io>
Cc: zihan zhou <15645113830zzh@gmail.com>,
bsegall@google.com, dietmar.eggemann@arm.com,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, mingo@redhat.com, rostedt@goodmis.org,
vincent.guittot@linaro.org, vschneid@redhat.com
Subject: Re: [PATCH V3 1/2] sched: Reduce the default slice to avoid tasks getting an extra tick
Date: Mon, 10 Feb 2025 10:13:52 +0100 [thread overview]
Message-ID: <20250210091352.GC10324@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250210012931.ym337oexdcjmwwzv@airbuntu>
On Mon, Feb 10, 2025 at 01:29:31AM +0000, Qais Yousef wrote:
> I brought the topic up of these magic values with Peter and Vincent in LPC as
> I think this logic is confusing. I have nothing against your patch, but if the
> maintainers agree I am in favour of removing it completely in favour of setting
> it to a single value that is the same across all systems.
You're talking about the scaling, right?
Yeah, it is of limited use. The cap at 8, combined with the fact that
its really hard to find a machine with less than 8 CPUs on, makes the
whole thing mostly useless.
Back when we did this, we still had dual-core laptops. Now phones have
8 or more CPUs on.
So I don't think I mind ripping it out.
next prev parent reply other threads:[~2025-02-10 9:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 7:48 [PATCH V3 0/2] sched: Reduce the default slice to avoid tasks getting an extra tick zihan zhou
2025-02-08 7:53 ` [PATCH V3 1/2] " zihan zhou
2025-02-10 1:29 ` Qais Yousef
2025-02-10 6:18 ` zihan zhou
2025-02-10 22:55 ` Qais Yousef
2025-02-10 9:13 ` Peter Zijlstra [this message]
2025-02-10 23:05 ` Qais Yousef
2025-02-22 3:19 ` zihan zhou
2025-02-23 0:08 ` Qais Yousef
2025-02-24 14:15 ` Vincent Guittot
2025-02-25 0:25 ` Qais Yousef
2025-02-25 1:29 ` Vincent Guittot
2025-02-25 10:13 ` Vincent Guittot
2025-02-25 13:06 ` Qais Yousef
2025-02-14 3:33 ` K Prateek Nayak
2025-02-22 3:02 ` zihan zhou
2025-03-07 4:10 ` K Prateek Nayak
2025-03-14 1:49 ` zihan zhou
2025-02-15 10:55 ` [tip: sched/core] " tip-bot2 for zihan zhou
2025-02-08 7:57 ` [PATCH V3 2/2] " zihan zhou
2025-02-08 19:32 ` Vincent Guittot
2025-02-10 6:26 ` zihan zhou
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=20250210091352.GC10324@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=15645113830zzh@gmail.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=qyousef@layalina.io \
--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