From: Tejun Heo <tj@kernel.org>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>,
sched-ext@lists.linux.dev, David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-7.2] sched_ext: Documentation: update scx_qmap description for BPF arena
Date: Sun, 19 Apr 2026 06:04:39 -1000 [thread overview]
Message-ID: <8f403734b8b8f9da6b71dc1804960f9c@kernel.org> (raw)
In-Reply-To: <20260418120058.1555036-1-yphbchou0911@gmail.com>
Hello,
Thanks for catching this, but the proposed phrasing is a bit misleading.
BPF_MAP_TYPE_ARENA isn't a queue-map replacement for BPF_MAP_TYPE_QUEUE
- the arena is just memory; the queueing now happens through intrusive
doubly-linked lists in arena with per-queue bpf_res_spin_lock.
How about matching the file-level description in scx_qmap.bpf.c?
For Documentation/scheduler/sched-ext.rst:
* ``scx_qmap[.bpf].c``: A multi-level FIFO scheduler supporting five
levels of priority implemented with arena-backed doubly-linked lists.
For tools/sched_ext/README.md:
Another simple, yet slightly more complex scheduler that provides an
example of a basic weighted FIFO queuing policy. It also provides
examples of some common useful BPF features, such as arena-backed
doubly-linked lists threaded through per-task context and
`bpf_res_spin_lock` for per-queue synchronization. It also illustrates
how core-sched support could be implemented.
Thanks.
--
tejun
parent reply other threads:[~2026-04-19 16:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260418120058.1555036-1-yphbchou0911@gmail.com>]
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=8f403734b8b8f9da6b71dc1804960f9c@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chia7712@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.com \
--cc=yphbchou0911@gmail.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