From: Boqun Feng <boqun.feng@gmail.com>
To: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>, "Tejun Heo" <tj@kernel.org>,
"Tamir Duberstein" <tamird@gmail.com>,
"Hamza Mahfooz" <hamzamahfooz@linux.microsoft.com>,
"Alban Kurti" <kurti@invicto.ai>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [RFC PATCH] rust: workqueue: Add an example for try_spawn()
Date: Wed, 30 Jul 2025 09:34:39 -0700 [thread overview]
Message-ID: <20250730163439.50753-1-boqun.feng@gmail.com> (raw)
`try_spawn()` could use an example to demonstrate the usage, and
arguably it's the most simple usage of workqueue in case someone needs a
deferred work, so add it.
Cc: Joel Fernandes <joelagnelf@nvidia.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
---
Miguel, Alice and Tejun, while I'm at it, should we also rename the
function to `spawn()` because of the motivation mentioned here [1]?
[1]: https://rust-for-linux.zulipchat.com/#narrow/channel/291566-Library/topic/.60new.60.20or.20.60try_new.60.3F/near/529533317
Also I find the `{ <clone> || { } }` is really good if I only need to
clone the Arc for passing to a callback closure, but I'm not sure how
people feel about it, so criticism is welcome ;-)
rust/kernel/workqueue.rs | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/rust/kernel/workqueue.rs b/rust/kernel/workqueue.rs
index b9343d5bc00f..59c1a5e14d12 100644
--- a/rust/kernel/workqueue.rs
+++ b/rust/kernel/workqueue.rs
@@ -331,6 +331,33 @@ pub fn enqueue_delayed<W, const ID: u64>(&self, w: W, delay: Jiffies) -> W::Enqu
/// Tries to spawn the given function or closure as a work item.
///
/// This method can fail because it allocates memory to store the work item.
+ ///
+ /// # Examples
+ ///
+ /// ```
+ /// use kernel::{alloc::flags, sync::{Arc, Completion, new_spinlock}, workqueue};
+ ///
+ /// let work_done = Arc::pin_init(Completion::new(), flags::GFP_KERNEL)?;
+ /// let data = Arc::pin_init(new_spinlock!(0), flags::GFP_KERNEL)?;
+ ///
+ /// workqueue::system().try_spawn(
+ /// flags::GFP_KERNEL,
+ /// {
+ /// let work_done = work_done.clone();
+ /// let data = data.clone();
+ /// move || {
+ /// *data.lock() = 42;
+ /// work_done.complete_all();
+ /// }
+ /// }
+ /// )?;
+ ///
+ /// work_done.wait_for_completion();
+ ///
+ /// // `work_done` being completed implies the observation of the write of `data` in the work.
+ /// assert_eq!(*data.lock(), 42);
+ /// # Ok::<(), Error>(())
+ /// ```
pub fn try_spawn<T: 'static + Send + FnOnce()>(
&self,
flags: Flags,
--
2.39.5 (Apple Git-154)
next reply other threads:[~2025-07-30 16:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 16:34 Boqun Feng [this message]
2025-07-30 16:38 ` Miguel Ojeda
2025-07-30 18:48 ` Boqun Feng
2025-07-30 17:40 ` Joel Fernandes
2025-07-30 19:28 ` Benno Lossin
2025-07-30 19:38 ` Boqun Feng
2025-07-31 9:30 ` Benno Lossin
2025-08-01 1:15 ` Boqun Feng
2025-08-01 8:54 ` Benno Lossin
2025-08-01 9:05 ` Alice Ryhl
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=20250730163439.50753-1-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=joelagnelf@nvidia.com \
--cc=kurti@invicto.ai \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tj@kernel.org \
--cc=tmgross@umich.edu \
/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®