From: Boqun Feng <boqun.feng@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: anna-maria@linutronix.de, frederic@kernel.org,
tglx@linutronix.de, jstultz@google.com, sboyd@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rust-for-linux@vger.kernel.org, andrew@lunn.ch,
hkallweit1@gmail.com, tmgross@umich.edu, ojeda@kernel.org,
alex.gaynor@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@samsung.com, aliceryhl@google.com, arnd@arndb.de
Subject: Re: [PATCH v4 4/7] rust: time: Add wrapper for fsleep function
Date: Fri, 25 Oct 2024 17:16:19 -0700 [thread overview]
Message-ID: <Zxw00wQAj4LpeU_t@Boquns-Mac-mini.local> (raw)
In-Reply-To: <ZxwVuceNORRAI7FV@Boquns-Mac-mini.local>
On Fri, Oct 25, 2024 at 03:03:37PM -0700, Boqun Feng wrote:
[...]
> > +/// Sleeps for a given duration at least.
> > +///
> > +/// Equivalent to the kernel's [`fsleep`], flexible sleep function,
> > +/// which automatically chooses the best sleep method based on a duration.
> > +///
> > +/// The function sleeps infinitely (MAX_JIFFY_OFFSET) if `Delta` is negative
> > +/// or exceedes i32::MAX milliseconds.
> > +///
>
> I know Miguel has made his suggestion:
>
> https://lore.kernel.org/rust-for-linux/CANiq72kWqSCSkUk1efZyAi+0ScNTtfALn+wiJY_aoQefu2TNvg@mail.gmail.com/
>
"made his suggestion" is probably a wrong statement from me, looking
back the emails, Miguel was simply talking about we should document this
and his assumption that `fsleep()` should inherit the behavior/semantics
of msecs_to_jiffies().
But yeah, I still suggest doing it differently, i.e. panic on negative
or exceeding i32::MAX milliseconds.
Regards,
Boqun
[...]
next prev parent reply other threads:[~2024-10-26 0:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 3:31 [PATCH v4 0/7] rust: Add IO polling FUJITA Tomonori
2024-10-25 3:31 ` [PATCH v4 1/7] rust: time: Add PartialEq/Eq/PartialOrd/Ord trait to Ktime FUJITA Tomonori
2024-10-25 4:29 ` Trevor Gross
2024-10-25 3:31 ` [PATCH v4 2/7] rust: time: Introduce Delta type FUJITA Tomonori
2024-10-25 22:33 ` Andrew Lunn
2024-10-25 3:31 ` [PATCH v4 3/7] rust: time: Introduce Instant type FUJITA Tomonori
2024-10-25 20:55 ` Boqun Feng
2024-10-25 3:31 ` [PATCH v4 4/7] rust: time: Add wrapper for fsleep function FUJITA Tomonori
2024-10-25 22:03 ` Boqun Feng
2024-10-26 0:16 ` Boqun Feng [this message]
2024-10-28 0:50 ` FUJITA Tomonori
2024-10-28 4:38 ` Boqun Feng
2024-10-28 23:30 ` FUJITA Tomonori
2024-10-29 7:55 ` Thomas Gleixner
2024-10-31 8:31 ` FUJITA Tomonori
2024-10-25 3:31 ` [PATCH v4 5/7] MAINTAINERS: rust: Add TIMEKEEPING and TIMER abstractions FUJITA Tomonori
2024-10-25 3:31 ` [PATCH v4 6/7] rust: Add read_poll_timeout functions FUJITA Tomonori
2024-10-25 3:31 ` [PATCH v4 7/7] net: phy: qt2025: Wait until PHY becomes ready FUJITA Tomonori
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=Zxw00wQAj4LpeU_t@Boquns-Mac-mini.local \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=frederic@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=hkallweit1@gmail.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--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).