From: Boqun Feng <boqun.feng@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: dirk.behme@de.bosch.com, andrew@lunn.ch, aliceryhl@google.com,
netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
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
Subject: Re: iopoll abstraction
Date: Thu, 3 Oct 2024 07:25:31 -0700 [thread overview]
Message-ID: <Zv6pW3Mn6qxHxTGE@boqun-archlinux> (raw)
In-Reply-To: <20241003.134518.2205814402977569500.fujita.tomonori@gmail.com>
On Thu, Oct 03, 2024 at 01:45:18PM +0000, FUJITA Tomonori wrote:
> On Thu, 3 Oct 2024 04:52:48 -0700
> Boqun Feng <boqun.feng@gmail.com> wrote:
>
> > You could use closure as a parameter to avoid macro interface, something
> > like:
> >
> > fn read_poll_timeout<Op, Cond, T>(
> > op: Op,
> > cond: Cond,
> > sleep: Delta,
> > timeout: Delta,
> > ) -> Result<T> where
> > Op: Fn() -> T,
> > cond: Fn() -> bool {
> >
> > let __timeout = kernel::Ktime::ktime_get() + timeout;
> >
> > let val = loop {
> > let val = op();
> > if cond() {
> > break Some(val);
> > }
> > kernel::delay::sleep(sleep);
> >
> > if __timeout.after(kernel::Ktime::ktime_get()) {
> > break None;
> > }
> > };
> >
> > if cond() {
> > val
> > } else {
> > Err(kernel::error::code::ETIMEDOUT)
> > }
> > }
>
> Great! I changed couple of things.
>
> 1. Op typically reads a value from a register and could need mut objects. So I use FnMut.
> 2. reading from hardware could fail so Op had better to return an error [1].
> 3. Cond needs val; typically check the value from a register.
>
> [1] https://lore.kernel.org/netdev/ec7267b5-ae77-4c4a-94f8-aa933c87a9a2@lunn.ch
>
> Seems that the following works QT2025 driver. How does it look?
>
Makes sense to me. Of course, more users will probably tell us whether
we cover all the cases, but this is a good starting point. I would put
the function at kernel::io::poll, but that's my personal preference ;-)
Regards,
Boqun
> fn read_poll_timeout<Op, Cond, T: Copy>(
> mut op: Op,
> cond: Cond,
> sleep: Delta,
> timeout: Delta,
> ) -> Result<T>
> where
> Op: FnMut() -> Result<T>,
> Cond: Fn(T) -> bool,
> {
> let timeout = Ktime::ktime_get() + timeout;
> let ret = loop {
> let val = op()?;
> if cond(val) {
> break Ok(val);
> }
> kernel::delay::sleep(sleep);
>
> if Ktime::ktime_get() > timeout {
> break Err(code::ETIMEDOUT);
> }
> };
>
> ret
> }
next prev parent reply other threads:[~2024-10-03 14:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:25 [PATCH net-next v1 0/2] add delay abstraction (sleep functions) FUJITA Tomonori
2024-10-01 11:25 ` [PATCH net-next v1 1/2] rust: add delay abstraction FUJITA Tomonori
2024-10-01 11:33 ` Alice Ryhl
2024-10-01 12:31 ` Andrew Lunn
2024-10-01 15:08 ` Miguel Ojeda
2024-10-02 11:34 ` FUJITA Tomonori
2024-10-02 12:18 ` Andrew Lunn
2024-10-02 12:35 ` Miguel Ojeda
2024-10-02 12:51 ` Andrew Lunn
2024-10-02 13:21 ` Miguel Ojeda
2024-10-02 20:04 ` Thomas Gleixner
2024-10-02 12:37 ` Alice Ryhl
2024-10-02 13:58 ` FUJITA Tomonori
2024-10-02 14:27 ` Alice Ryhl
2024-10-02 14:40 ` FUJITA Tomonori
2024-10-02 14:52 ` Miguel Ojeda
2024-10-02 19:40 ` Thomas Gleixner
2024-10-03 1:24 ` FUJITA Tomonori
2024-10-03 10:50 ` Miguel Ojeda
2024-10-03 12:33 ` Andrew Lunn
2024-10-04 12:08 ` FUJITA Tomonori
2024-10-04 14:08 ` Andrew Lunn
2024-10-01 11:25 ` [PATCH net-next v1 2/2] net: phy: qt2025: wait until PHY becomes ready FUJITA Tomonori
2024-10-01 11:36 ` Alice Ryhl
2024-10-01 12:48 ` Andrew Lunn
2024-10-02 4:39 ` iopoll abstraction (was: Re: [PATCH net-next v1 2/2] net: phy: qt2025: wait until PHY becomes ready) Dirk Behme
2024-10-02 9:56 ` iopoll abstraction FUJITA Tomonori
2024-10-03 11:52 ` Boqun Feng
2024-10-03 13:45 ` FUJITA Tomonori
2024-10-03 14:25 ` Boqun Feng [this message]
2024-10-03 16:00 ` Andrew Lunn
2024-10-04 11:54 ` FUJITA Tomonori
2024-10-03 16:09 ` Andrew Lunn
2024-10-04 11:48 ` FUJITA Tomonori
2024-10-04 13:37 ` Andrew Lunn
2024-10-02 10:13 ` [PATCH net-next v1 2/2] net: phy: qt2025: wait until PHY becomes ready FUJITA Tomonori
2024-10-02 12:31 ` Andrew Lunn
2024-10-03 5:07 ` FUJITA Tomonori
2024-10-02 11:17 ` FUJITA Tomonori
2024-10-01 11:39 ` [PATCH net-next v1 0/2] add delay abstraction (sleep functions) 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=Zv6pW3Mn6qxHxTGE@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=dirk.behme@de.bosch.com \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.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).