From: Boqun Feng <boqun.feng@gmail.com>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Alice Ryhl <aliceryhl@google.com>
Subject: Re: [PATCH v3 2/2] rust: add system_percpu() around the new system_percpu_wq
Date: Wed, 8 Oct 2025 08:56:04 -0700 [thread overview]
Message-ID: <aOaJlHEPzHcAdcUx@tardis-2.local> (raw)
In-Reply-To: <20251008151554.340806-3-marco.crivellari@suse.com>
On Wed, Oct 08, 2025 at 05:15:54PM +0200, Marco Crivellari wrote:
> The C code defines 2 new workqueues: system_percpu_wq and system_dfl_wq,
> respectively the futures replacement for system_wq and system_unbound_wq.
>
> This change introduce system_percpu(), that use the new system_percpu_wq.
>
> system_wq will be replaced in a future release cycle and should
> not be used.
>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
If we were to expose the system_percpu_wq to Rust, then we should also
add queue_work_on() API to Rust, otherwise it's kinda pointless IMO.
PS. We can use the CpuId abstraction:
http://rust.docs.kernel.org/kernel/cpu/struct.CpuId.html
and have an API like:
ipml Queue {
pub fn queue_on(&self, cpu: CpuId, w: W) -> W::EqueueOutput
}
or maybe a different new type `PerCpuQueue`?
Regards,
Boqun
> ---
> rust/kernel/workqueue.rs | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/rust/kernel/workqueue.rs b/rust/kernel/workqueue.rs
> index 300cc2bfe012..05f213444b91 100644
> --- a/rust/kernel/workqueue.rs
> +++ b/rust/kernel/workqueue.rs
> @@ -940,11 +940,26 @@ unsafe impl<T, const ID: u64> RawDelayedWorkItem<ID> for Pin<KBox<T>>
> /// users which expect relatively short queue flush time.
> ///
> /// Callers shouldn't queue work items which can run for too long.
> +///
> +/// Note: `system_wq` will be removed in a future release cycle. Use [`system_percpu_wq`] instead.
> pub fn system() -> &'static Queue {
> // SAFETY: `system_wq` is a C global, always available.
> unsafe { Queue::from_raw(bindings::system_wq) }
> }
>
> +/// Returns the system work queue (`system_percpu_wq`).
> +///
> +/// It is the one used by `schedule[_delayed]_work[_on]()`. Multi-CPU multi-threaded. There are
> +/// users which expect relatively short queue flush time.
> +///
> +/// Callers shouldn't queue work items which can run for too long.
> +///
> +/// Note: `system_percpu_wq` will replace ['system_wq`] in a future relase cycle.
> +pub fn system_percpu() -> &'static Queue {
> + // SAFETY: `system_percpu_wq` is a C global, always available.
> + unsafe { Queue::from_raw(bindings::system_percpu_wq) }
> +}
> +
> /// Returns the system high-priority work queue (`system_highpri_wq`).
> ///
> /// It is similar to the one returned by [`system`] but for work items which require higher
> --
> 2.51.0
>
next prev parent reply other threads:[~2025-10-08 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 15:15 [PATCH v3 0/2] rust: add new workqueue functions Marco Crivellari
2025-10-08 15:15 ` [PATCH v3 1/2] rust: add system_dfl() around the new system_dfl_wq Marco Crivellari
2025-10-08 15:15 ` [PATCH v3 2/2] rust: add system_percpu() around the new system_percpu_wq Marco Crivellari
2025-10-08 15:56 ` Boqun Feng [this message]
2025-10-09 11:17 ` Alice Ryhl
2026-01-09 16:32 ` Marco Crivellari
2026-01-12 9:05 ` Alice Ryhl
2026-01-12 16:10 ` Marco Crivellari
2026-01-12 16:22 ` Alice Ryhl
2026-01-26 15:45 ` Marco Crivellari
2026-02-03 8:41 ` Marco Crivellari
2026-02-03 10:19 ` Alice Ryhl
2025-10-08 16:20 ` Miguel Ojeda
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=aOaJlHEPzHcAdcUx@tardis-2.local \
--to=boqun.feng@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®