rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Benno Lossin" <lossin@kernel.org>
To: "Boqun Feng" <boqun.feng@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"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: Re: [RFC PATCH] rust: workqueue: Add an example for try_spawn()
Date: Thu, 31 Jul 2025 11:30:10 +0200	[thread overview]
Message-ID: <DBQ4VKUDJOF4.1JVIM88YK8V59@kernel.org> (raw)
In-Reply-To: <aIp0uo5y9O551HW9@tardis-2.local>

On Wed Jul 30, 2025 at 9:38 PM CEST, Boqun Feng wrote:
> On Wed, Jul 30, 2025 at 09:28:05PM +0200, Benno Lossin wrote:
>> On Wed Jul 30, 2025 at 6:34 PM CEST, Boqun Feng wrote:
>> > +    /// 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();
>> > +    ///         }
>> > +    ///     }
>> > +    /// )?;
>> 
>> Not doing your pattern and instead adding a `2` postfix we get:
>> 
>>     let work_done2 = work_done.clone();
>>     let data2 = data.clone();
>> 
>
> Yeah, the thing I want to achieve with my pattern is: make it clear that
> the work and the task that queues the work are sharing the same
> `work_done` and `data` (well, no the same `Arc` exactly, but the `Arc`s
> that are pointing to the same object). This pattern here doesn't show
> that clearly imo.

I think it's fine, that pattern is often used for that. Not heavily
opposed to doing it your way, but I feel like the code looks a bit weird
& my instinct is to move the let bindings out (which would produce code
that doesn't compile).

> That said, I'm not really against using `work_done2` and `data2`, just
> I'm afraid that may be more confusing.

I don't think that's a problem.

>>     workqueue::system().try_spawn(flags::GFP_KERNEL, move || {
>>         *data2.lock() = 42;
>>         work_done2.complete_all();
>>     })?;
>> 
>> There are some discussions of introducing some better syntax for (cheap)
>> cloning, so maybe we can use that in the future.
>
> Do you have links to these discussions.

It's an RFC:

    https://github.com/rust-lang/rfcs/pull/368

There probably are more discussions on zulip, but I haven't read those.
The RFC also has a project goal:

    https://rust-lang.github.io/rust-project-goals/2025h2/ergonomic-rc.html

---
Cheers,
Benno

  reply	other threads:[~2025-07-31  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30 16:34 [RFC PATCH] rust: workqueue: Add an example for try_spawn() Boqun Feng
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 [this message]
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=DBQ4VKUDJOF4.1JVIM88YK8V59@kernel.org \
    --to=lossin@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.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=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;
as well as URLs for NNTP newsgroup(s).