[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250225122705.GD34233@noisy.programming.kicks-ass.net>
Date: Tue, 25 Feb 2025 13:27:05 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Chen Yu <yu.chen.surf@...mail.com>
Cc: zihan zhou <15645113830zzh@...il.com>, oe-lkp@...ts.linux.dev,
kernel test robot <oliver.sang@...el.com>, lkp@...el.com,
linux-kernel@...r.kernel.org, x86@...nel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
aubrey.li@...ux.intel.com, yu.c.chen@...el.com
Subject: Re: [tip:sched/core] [sched] 2ae891b826: hackbench.throughput 6.2%
regression
On Tue, Feb 25, 2025 at 05:31:34PM +0800, Chen Yu wrote:
>
> But consider that the 6% regression is not that high, and the user might customize
> base_slice via debugfs on-demand, we can keep an eye on this and revist it in the
> future(we have encountered some SPECjbb regression due to over-preemption).
You can specify a per-task slice using sched_attr::sched_runtime. Also
see commit 857b158dc5e8 ("sched/eevdf: Use sched_attr::sched_runtime to
set request/slice suggestion")
Powered by blists - more mailing lists