Received-SPF: pass (google.com: domain of linux-kernel+bounces-42545-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Mon, 29 Jan 2024 18:36:25 +0800
From: Wang Jinchao <wangjinchao@xfusion.com>
To: Ingo Molnar <mingo@redhat.com>, Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>, Vincent Guittot
	<vincent.guittot@linaro.org>, Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>, Ben Segall <bsegall@google.com>, Mel
 Gorman <mgorman@suse.de>, Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>, <linux-kernel@vger.kernel.org>
CC: <stone.xulei@xfusion.com>
Subject: [RFC resend] sched: Can we rename 'core scheduling' to 'smt
 scheduling'?
Message-ID: <Zbd/qYQCQCELe+TF@fedora>
References: <202312191503+0800-wangjinchao@xfusion.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <202312191503+0800-wangjinchao@xfusion.com>

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.