Rust for Linux List
 help / color / mirror / Atom feed
From: FUJITA Tomonori <tomo@flapping.org>
To: gary@garyguo.net
Cc: tomo@flapping.org, 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, tkjos@android.com, tj@kernel.org,
	acourbot@nvidia.com, anna-maria@linutronix.de,
	bjorn3_gh@protonmail.com, dakr@kernel.org,
	daniel.almeida@collabora.com, frederic@kernel.org,
	jiangshanlai@gmail.com, 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, fujita.tomonori@gmail.com
Subject: Re: [PATCH v7 2/2] rust: sync: condvar: use Delta<Jiffy> for timeout and result
Date: Thu, 01 Oct 2026 11:09:15 +0900 (JST)	[thread overview]
Message-ID: <20261001.110915.1628653335575187641.tomo@flapping.org> (raw)
In-Reply-To: <DLT38GATZIIR.1LX8EXAFFGJX9@garyguo.net>

On Thu, 01 Oct 2026 01:50:41 +0100
"Gary Guo" <gary@garyguo.net> wrote:

>> diff --git a/drivers/android/binder/process.rs b/drivers/android/binder/process.rs
>> index 5372bfbd93b3..ca944a50c6eb 100644
>> --- a/drivers/android/binder/process.rs
>> +++ b/drivers/android/binder/process.rs
>> @@ -35,6 +35,7 @@
>>          Arc, ArcBorrow, CondVar, CondVarTimeoutResult, SetOnce, SpinLock, UniqueArc,
>>      },
>>      task::{Pid, Task},
>> +    time::Delta,
>>      uaccess::{UserSlice, UserSliceReader},
>>      uapi,
>>      workqueue::{self, Work},
>> @@ -1549,8 +1550,8 @@ pub(crate) fn ioctl_freeze(&self, info: &BinderFreezeInfo) -> Result {
>>          inner.is_frozen = IsFrozen::InProgress;
>>  
>>          if info.timeout_ms > 0 {
>> -            let mut jiffies = kernel::time::msecs_to_jiffies(info.timeout_ms);
>> -            while jiffies > 0 {
>> +            let mut jiffies = Delta::from_millis(info.timeout_ms.into()).to_jiffies_timeout();
>> +            while jiffies.as_jiffies() > 0 {
>>                  if inner.outstanding_txns == 0 {
>>                      break;
>>                  }
>> @@ -1567,7 +1568,7 @@ pub(crate) fn ioctl_freeze(&self, info: &BinderFreezeInfo) -> Result {
>>                          jiffies = remaining;
>>                      }
>>                      CondVarTimeoutResult::Timeout => {
>> -                        jiffies = 0;
>> +                        jiffies = Delta::from_jiffies(0);
> 
> Hmm, we should make `Delta::ZERO` work for jiffies too.

Agreed. I'll add a patch for it in v8.

>> @@ -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),
> 
> This pattern shows up many times..
> 
> Makes me wonder if we want a `Duration` type that is `Delta` but unsigned (value
> range restricted between 0..isize::MAX (or i64::MAX for Nsec).
> 
> Or just have a `as_jiffies_unsigned()` which does the clamp.

I think Delta should stay signed. Once we have Instant for jiffies,
the difference of two instants can be negative, for example a deadline
minus the current jiffies. This is a common pattern in C.

I'll add as_jiffies_unsigned() in v8. It clamps a negative value to 0
and returns unsigned long.

      reply	other threads:[~2026-10-01  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  1:41 [PATCH v7 0/2] rust: use Delta instead of raw jiffies for timeouts and delays FUJITA Tomonori
2026-09-30  1:41 ` [PATCH v7 1/2] rust: workqueue: take a Delta<Jiffy> for the enqueue delay FUJITA Tomonori
2026-09-30  1:41 ` [PATCH v7 2/2] rust: sync: condvar: use Delta<Jiffy> for timeout and result FUJITA Tomonori
2026-10-01  0:50   ` Gary Guo
2026-10-01  2:09     ` FUJITA Tomonori [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=20261001.110915.1628653335575187641.tomo@flapping.org \
    --to=tomo@flapping.org \
    --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=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiangshanlai@gmail.com \
    --cc=jstultz@google.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox