[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250513170344.3621-1-jake@jakerice.dev>
Date: Tue, 13 May 2025 13:03:44 -0400
From: Jake Rice <jake@...erice.dev>
To: corbet@....net,
linux-doc@...r.kernel.org
Cc: tj@...nel.org,
arighi@...dia.com,
changwoo@...lia.com,
ggherdovich@...e.com,
me@...tlynerdless.de,
ake@...erice.dev,
abovard@...ux.ibm.com,
devaanshk840@...il.com,
cengiz@...nel.wtf,
linux-kernel@...r.kernel.org,
Jake Rice <jake@...erice.dev>
Subject: [PATCH] Documentation: scheduler: Changed lowercase acronyms to uppercase
Everywhere else in this doc, the dispatch queue acronym (DSQ) is
uppercase. There were a couple places where the acronym was written in
lowercase. I changed them to uppercase to make it homogeneous.
Signed-off-by: Jake Rice <jake@...erice.dev>
---
Documentation/scheduler/sched-ext.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/scheduler/sched-ext.rst b/Documentation/scheduler/sched-ext.rst
index 0b2654e2164b..878762b6379d 100644
--- a/Documentation/scheduler/sched-ext.rst
+++ b/Documentation/scheduler/sched-ext.rst
@@ -197,8 +197,8 @@ Dispatch Queues
To match the impedance between the scheduler core and the BPF scheduler,
sched_ext uses DSQs (dispatch queues) which can operate as both a FIFO and a
priority queue. By default, there is one global FIFO (``SCX_DSQ_GLOBAL``),
-and one local dsq per CPU (``SCX_DSQ_LOCAL``). The BPF scheduler can manage
-an arbitrary number of dsq's using ``scx_bpf_create_dsq()`` and
+and one local DSQ per CPU (``SCX_DSQ_LOCAL``). The BPF scheduler can manage
+an arbitrary number of DSQs using ``scx_bpf_create_dsq()`` and
``scx_bpf_destroy_dsq()``.
A CPU always executes a task from its local DSQ. A task is "inserted" into a
--
2.34.1
Powered by blists - more mailing lists