public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs
@ 2024-11-10 20:02 Tejun Heo
  2024-11-10 20:02 ` [PATCH 1/3] sched_ext: Rename scx_bpf_dispatch[_vtime]() to scx_bpf_dsq_insert[_vtime]() Tejun Heo
                   ` (6 more replies)
  0 siblings, 7 replies; 12+ messages in thread
From: Tejun Heo @ 2024-11-10 20:02 UTC (permalink / raw)
  To: void
  Cc: linux-kernel, kernel-team, sched-ext, arighi, multics69, me,
	ggherdovich, dschatzberg, yougmark94

Hello,

[v1] -> v2: Comment and documentation updates.

In sched_ext API, a repeatedly reported pain point is the overuse of the
verb "dispatch" and confusion around "consume":

- ops.dispatch()
- scx_bpf_dispatch[_vtime]()
- scx_bpf_consume()
- scx_bpf_dispatch[_vtime]_from_dsq*()

This overloading of the term is historical. Originally, there were only
built-in DSQs and moving a task into a DSQ always dispatched it for
execution. Using the verb "dispatch" for the kfuncs to move tasks into these
DSQs made sense.

Later, user DSQs were added and scx_bpf_dispatch[_vtime]() updated to be
able to insert tasks into any DSQ. The only allowed DSQ to DSQ transfer was
from a non-local DSQ to a local DSQ and this operation was named "consume".
This was already confusing as a task could be dispatched to a user DSQ from
ops.enqueue() and then the DSQ would have to be consumed in ops.dispatch().
Later addition of scx_bpf_dispatch_from_dsq*() made the confusion even worse
as "dispatch" in this context meant moving a task to an arbitrary DSQ from a
user DSQ.

Clean up the API with the following renames:

1. scx_bpf_dispatch[_vtime]()		-> scx_bpf_dsq_insert[_vtime]()
2. scx_bpf_consume()			-> scx_bpf_dsq_move_to_local()
3. scx_bpf_dispatch[_vtime]_from_dsq*()	-> scx_bpf_dsq_move[_vtime]*()

This patchset is on top of sched_ext/for-6.13 72b85bf6a7f6 ("sched_ext:
scx_bpf_dispatch_from_dsq_set_*() are allowed from unlocked context") and
contains the following patches:

 0001-sched_ext-Rename-scx_bpf_dispatch-_vtime-to-scx_bpf_.patch
 0002-sched_ext-Rename-scx_bpf_consume-to-scx_bpf_dsq_move.patch
 0003-sched_ext-Rename-scx_bpf_dispatch-_vtime-_from_dsq-s.patch

and is always available in the following git branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-api-rename-dispatch-v2

diffstat follows. Thanks.

 Documentation/scheduler/sched-ext.rst    |   71 ++++++-------
 kernel/sched/ext.c                       |  243 +++++++++++++++++++++++++++++-----------------
 tools/sched_ext/include/scx/common.bpf.h |   18 +--
 tools/sched_ext/include/scx/compat.bpf.h |  117 +++++++++++++++++++---
 tools/sched_ext/scx_central.bpf.c        |   14 +-
 tools/sched_ext/scx_flatcg.bpf.c         |   20 ++-
 tools/sched_ext/scx_qmap.bpf.c           |   36 +++---
 tools/sched_ext/scx_simple.bpf.c         |   16 +--
 8 files changed, 348 insertions(+), 187 deletions(-)

--
tejun

[v2] http://lkml.kernel.org/r/20241109194853.580310-1-tj@kernel.org

^ permalink raw reply	[flat|nested] 12+ messages in thread
* [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs
@ 2024-11-09 19:48 Tejun Heo
  2024-11-10 11:45 ` Andrea Righi
  0 siblings, 1 reply; 12+ messages in thread
From: Tejun Heo @ 2024-11-09 19:48 UTC (permalink / raw)
  To: void
  Cc: linux-kernel, kernel-team, sched-ext, arighi, multics69, me,
	ggherdovich, dschatzberg, yougmark94

In sched_ext API, a repeatedly reported pain point is the overuse of the
verb "dispatch" and confusion around "consume":

- ops.dispatch()
- scx_bpf_dispatch[_vtime]()
- scx_bpf_consume()
- scx_bpf_dispatch[_vtime]_from_dsq*()

This overloading of the term is historical. Originally, there were only
built-in DSQs and moving a task into a DSQ always dispatched it for
execution. Using the verb "dispatch" for the kfuncs to move tasks into these
DSQs made sense.

Later, user DSQs were added and scx_bpf_dispatch[_vtime]() updated to be
able to insert tasks into any DSQ. The only allowed DSQ to DSQ transfer was
from a non-local DSQ to a local DSQ and this operation was named "consume".
This was already confusing as a task could be dispatched to a user DSQ from
ops.enqueue() and then the DSQ would have to be consumed in ops.dispatch().
Later addition of scx_bpf_dispatch_from_dsq*() made the confusion even worse
as "dispatch" in this context meant moving a task to an arbitrary DSQ from a
user DSQ.

Clean up the API with the following renames:

1. scx_bpf_dispatch[_vtime]()		-> scx_bpf_dsq_insert[_vtime]()
2. scx_bpf_consume()			-> scx_bpf_dsq_move_to_local()
3. scx_bpf_dispatch[_vtime]_from_dsq*()	-> scx_bpf_dsq_move[_vtime]*()

This patchset is on top of sched_ext/for-6.13 72b85bf6a7f6 ("sched_ext:
scx_bpf_dispatch_from_dsq_set_*() are allowed from unlocked context") and
contains the following patches:

 0001-sched_ext-Rename-scx_bpf_dispatch-_vtime-to-scx_bpf_.patch
 0002-sched_ext-Rename-scx_bpf_consume-to-scx_bpf_dsq_move.patch
 0003-sched_ext-Rename-scx_bpf_dispatch-_vtime-_from_dsq-s.patch

and is always available in the following git branch:

 git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git scx-api-rename-dispatch

diffstat follows. Thanks.

 kernel/sched/ext.c                       |  238 +++++++++++++++++++++++++++++++++--------------------
 tools/sched_ext/include/scx/common.bpf.h |   18 ++--
 tools/sched_ext/include/scx/compat.bpf.h |  117 +++++++++++++++++++++++---
 tools/sched_ext/scx_central.bpf.c        |   14 +--
 tools/sched_ext/scx_flatcg.bpf.c         |   20 ++--
 tools/sched_ext/scx_qmap.bpf.c           |   36 ++++----
 tools/sched_ext/scx_simple.bpf.c         |   16 +--
 7 files changed, 308 insertions(+), 151 deletions(-)

--
tejun

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2024-11-12 16:56 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-11-10 20:02 [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs Tejun Heo
2024-11-10 20:02 ` [PATCH 1/3] sched_ext: Rename scx_bpf_dispatch[_vtime]() to scx_bpf_dsq_insert[_vtime]() Tejun Heo
2024-11-10 20:02 ` [PATCH 2/3] sched_ext: Rename scx_bpf_consume() to scx_bpf_dsq_move_to_local() Tejun Heo
2024-11-10 20:02 ` [PATCH 3/3] sched_ext: Rename scx_bpf_dispatch[_vtime]_from_dsq*() -> scx_bpf_dsq_move[_vtime]*() Tejun Heo
2024-11-11 16:02   ` Giovanni Gherdovich
2024-11-10 20:17 ` [PATCHSET sched_ext/for-6.13] sched_ext: Rename dispatch and consume kfuncs Andrea Righi
2024-11-11  1:40 ` Changwoo Min
2024-11-11  8:51   ` Johannes Bechberger
2024-11-11 17:07 ` Tejun Heo
2024-11-12 16:56 ` David Vernet
  -- strict thread matches above, loose matches on Subject: below --
2024-11-09 19:48 Tejun Heo
2024-11-10 11:45 ` Andrea Righi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox