linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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'?
Date: Mon, 29 Jan 2024 18:36:25 +0800	[thread overview]
Message-ID: <Zbd/qYQCQCELe+TF@fedora> (raw)
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.

      reply	other threads:[~2024-01-29 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  7:07 [RFC] sched: Can we rename 'core scheduling' to 'smt scheduling'? Wang Jinchao
2024-01-29 10:36 ` Wang Jinchao [this message]

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=Zbd/qYQCQCELe+TF@fedora \
    --to=wangjinchao@xfusion.com \
    --cc=bristot@redhat.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=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=stone.xulei@xfusion.com \
    --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;
as well as URLs for NNTP newsgroup(s).