From: "Gary Guo" <gary@garyguo.net>
To: "FUJITA Tomonori" <tomo@flapping.org>, <gary@garyguo.net>
Cc: <a.hindborg@kernel.org>, <aliceryhl@google.com>,
<arve@android.com>, <boqun@kernel.org>, <brauner@kernel.org>,
<cmllamas@google.com>, <gregkh@linuxfoundation.org>,
<ojeda@kernel.org>, <tj@kernel.org>, <tkjos@android.com>,
<acourbot@nvidia.com>, <anna-maria@linutronix.de>,
<bjorn3_gh@protonmail.com>, <dakr@kernel.org>,
<daniel.almeida@collabora.com>, <frederic@kernel.org>,
<jstultz@google.com>, <lossin@kernel.org>, <lyude@redhat.com>,
<sboyd@kernel.org>, <tamird@kernel.org>, <tglx@kernel.org>,
<tmgross@umich.edu>, <work@onurozkan.dev>,
<rust-for-linux@vger.kernel.org>, <jiangshanlai@gmail.com>,
<markus.probst@posteo.de>, <fujita.tomonori@gmail.com>
Subject: Re: [PATCH v8 4/4] rust: sync: condvar: use Delta<Jiffy> for timeout and result
Date: Fri, 02 Oct 2026 14:03:30 +0100 [thread overview]
Message-ID: <DLUDG2TH77RI.ZQ0T5MH7Q573@garyguo.net> (raw)
In-Reply-To: <20261002.200545.48892805627139274.tomo@flapping.org>
On Fri Oct 2, 2026 at 12:05 PM BST, FUJITA Tomonori wrote:
> On Fri, 02 Oct 2026 11:00:40 +0100
> "Gary Guo" <gary@garyguo.net> wrote:
>
>> On Fri Oct 2, 2026 at 6:04 AM BST, FUJITA Tomonori wrote:
>>> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> [...]
>
>>> @@ -182,19 +185,29 @@ pub fn wait_interruptible_freezable<T: ?Sized, B: Backend>(
>>> /// Atomically releases the given lock (whose ownership is proven by the guard) and puts the
>>> /// thread to sleep. It wakes up when notified by [`CondVar::notify_one`] or
>>> /// [`CondVar::notify_all`], or when a timeout occurs, or when the thread receives a signal.
>>> + ///
>>> + /// A negative timeout is treated as zero.
>>> #[must_use = "wait_interruptible_timeout returns if a signal is pending, so the caller must check the return value"]
>>> pub fn wait_interruptible_timeout<T: ?Sized, B: Backend>(
>>> &self,
>>> guard: &mut Guard<'_, T, B>,
>>> - jiffies: Jiffies,
>>> + delta: Delta<Jiffy>,
>>> ) -> CondVarTimeoutResult {
>>> - let jiffies = jiffies.try_into().unwrap_or(MAX_SCHEDULE_TIMEOUT);
>>> - let res = self.wait_internal(TASK_INTERRUPTIBLE, guard, jiffies);
>>> + let jiffies = delta.as_jiffies();
>>> + let res = self.wait_internal(
>>> + TASK_INTERRUPTIBLE,
>>> + guard,
>>> + jiffies.clamp(0, MAX_SCHEDULE_TIMEOUT),
>>
>> I suppose this can be `delta.as_jiffies_unsigned()` too, although the clamp
>> makes it more explicit?
>
> wait_internal() takes isize, so with as_jiffies_unsigned() we
> need to cast the value back:
>
> | // CAST: `as_jiffies_unsigned()` returns at most `isize::MAX`, so the
> | // value fits in `isize`.
> | let jiffies = delta.as_jiffies_unsigned() as isize;
> | let res = self.wait_internal(TASK_INTERRUPTIBLE, guard, jiffies);
>
> The clamp needs no cast, so I'd keep it.
Right, sounds reasonable. This can also be `isize::max(delta.as_jiffies(), 0)` I
suppose, but `clamp` reads fine too.
Best,
Gary
next prev parent reply other threads:[~2026-10-02 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uhEZnSETYdRTGg0YbynELBmOxAIhnGrslFSPb14RUm57hPflUhCWVyZ6zzbLwhu6_fx6hv9DSrHnMCGE3v4sIQ==@protonmail.internalid>
2026-10-02 5:04 ` [PATCH v8 0/4] rust: use Delta instead of raw jiffies for timeouts and delays FUJITA Tomonori
2026-10-02 5:04 ` [PATCH v8 1/4] rust: time: make Delta::ZERO generic over the time unit FUJITA Tomonori
2026-10-08 12:54 ` Andreas Hindborg
2026-10-02 5:04 ` [PATCH v8 2/4] rust: time: add Delta::as_jiffies_unsigned() FUJITA Tomonori
2026-10-08 12:55 ` Andreas Hindborg
2026-10-02 5:04 ` [PATCH v8 3/4] rust: workqueue: take a Delta<Jiffy> for the enqueue delay FUJITA Tomonori
2026-10-02 5:04 ` [PATCH v8 4/4] rust: sync: condvar: use Delta<Jiffy> for timeout and result FUJITA Tomonori
2026-10-02 10:00 ` Gary Guo
2026-10-02 11:05 ` FUJITA Tomonori
2026-10-02 13:03 ` Gary Guo [this message]
2026-10-02 10:01 ` [PATCH v8 0/4] rust: use Delta instead of raw jiffies for timeouts and delays Gary Guo
2026-10-08 12:57 ` Andreas Hindborg
2026-10-12 5:42 ` 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=DLUDG2TH77RI.ZQ0T5MH7Q573@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=anna-maria@linutronix.de \
--cc=arve@android.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=jstultz@google.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=markus.probst@posteo.de \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tamird@kernel.org \
--cc=tglx@kernel.org \
--cc=tj@kernel.org \
--cc=tkjos@android.com \
--cc=tmgross@umich.edu \
--cc=tomo@flapping.org \
--cc=work@onurozkan.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.