lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 29 Jan 2024 18:36:25 +0800
From: Wang Jinchao <wangjinchao@...sion.com>
To: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
	Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot
	<vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>,
	Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>, Mel
 Gorman <mgorman@...e.de>, Daniel Bristot de Oliveira <bristot@...hat.com>,
	Valentin Schneider <vschneid@...hat.com>, <linux-kernel@...r.kernel.org>
CC: <stone.xulei@...sion.com>
Subject: [RFC resend] sched: Can we rename 'core scheduling' to 'smt
 scheduling'?

On Tue, Dec 19, 2023 at 03:07:43PM +0800, Wang Jinchao wrote:
> The term 'core' in 'kernel/sched/' implies a relation to the kernel of sched,
> and at the same time, 'core' is used in 'core scheduling' to represent a CPU core.
> Both meanings coexist in the 'core.c' file and appear numerous times.
> 
> This can be confusing for newcomers.
> 
> --
> Wang Jinchao

Maybe we should rename sched/core_sched.c to sched/smt_sched.c, 
and move relevant code from sched/core.c to smt_sched.c.
I believe using "smt" in smt_sched.c would be clearer than "core" in core_sched.c, 
especially considering its association with core.c.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ