rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alice Ryhl <aliceryhl@google.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>
Subject: Re: [PATCH 0/2] rust: replace wq users and add WQ_PERCPU to alloc_workqueue() users
Date: Mon, 8 Sep 2025 12:27:08 +0200	[thread overview]
Message-ID: <CAH5fLghpysJv5wt1ANPN+SHE2At8J6MHso7F1HdnNLomqniBrg@mail.gmail.com> (raw)
In-Reply-To: <CAAofZF77saPdGYXt-oYkfV=2pRCRtso5eJuw+FqmS8b8WERgOA@mail.gmail.com>

On Mon, Sep 8, 2025 at 12:24 PM Marco Crivellari
<marco.crivellari@suse.com> wrote:
>
> On Sun, Sep 7, 2025 at 12:59 PM Alice Ryhl <aliceryhl@google.com> wrote:
> > I mean that instead of:
> >
> > +/// Returns the system unbound work queue (`system_dfl_wq`).
> >  ///
> >  /// Workers are not bound to any specific CPU, not concurrency managed, and all queued work items
> >  /// are executed immediately as long as `max_active` limit is not reached and resources are
> >  /// available.
> >  pub fn system_unbound() -> &'static Queue {
> > -    // SAFETY: `system_unbound_wq` is a C global, always available.
> > -    unsafe { Queue::from_raw(bindings::system_unbound_wq) }
> > +    // SAFETY: `system_dfl_wq` is a C global, always available.
> > +    unsafe { Queue::from_raw(bindings::system_dfl_wq) }
> >  }
> >
> > you add a new function:
> >
> >         pub fn system_dfl() -> &'static Queue {
> >             // SAFETY: `system_dfl_wq` is a C global, always available.
> >             unsafe { Queue::from_raw(bindings::system_dfl_wq) }
> >         }
> >
> > and do *not* modify system_unbound().
> >
> > Alice
>
> Hello Alice,
>
> Ah, perfect. Yes it makes sense this change, you're right.
> I will send the v2 introducing the new functions for both the patches
> in this series.
>
> It would also make sense to also change the above comment, mentioning that
> system_unbound() uses a wq that will be removed in the future, and so
> it is better to
> use system_dfl() instead?
>
> I'm thinking to something like:
>
> +///
> +/// Note: system_unbound_wq will be removed in a future release
> cycle. Use system_dfl_wq instead.
> pub fn system_unbound() -> &'static Queue {
>     // SAFETY: `system_unbound_wq` is a C global, always available.
>     unsafe { Queue::from_raw(bindings::system_unbound_wq) }
> }
>
> +pub fn system_dfl() -> &'static Queue {
> +    // SAFETY: `system_dfl_wq` is a C global, always available.
> +    unsafe { Queue::from_raw(bindings::system_dfl_wq) }
> +}
>
> Sounds good?

That is reasonable, yes. Please make it a link:

/// Note: `system_unbound_wq` will be removed in a future release
cycle. Use [`system_dfl`] instead.

Alice

      reply	other threads:[~2025-09-08 10:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05  9:08 [PATCH 0/2] rust: replace wq users and add WQ_PERCPU to alloc_workqueue() users Marco Crivellari
2025-09-05  9:08 ` [PATCH 1/2] rust: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-09-05  9:08 ` [PATCH 2/2] rust: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-09-05 11:33 ` [PATCH 0/2] rust: replace wq users and add WQ_PERCPU to alloc_workqueue() users Alice Ryhl
2025-09-05 16:05   ` Marco Crivellari
2025-09-07 10:59     ` Alice Ryhl
2025-09-08 10:24       ` Marco Crivellari
2025-09-08 10:27         ` Alice Ryhl [this message]

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=CAH5fLghpysJv5wt1ANPN+SHE2At8J6MHso7F1HdnNLomqniBrg@mail.gmail.com \
    --to=aliceryhl@google.com \
    --cc=alex.gaynor@gmail.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;
as well as URLs for NNTP newsgroup(s).