From: der.herr@hofr.at (Nicholas Mc Guire)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to use wait_event_interruptible_timeout with less than 1 jiffie timeout?
Date: Wed, 20 Jan 2016 15:01:09 +0000 [thread overview]
Message-ID: <20160120150109.GC16707@osadl.at> (raw)
In-Reply-To: <87a8o0s7nk.fsf@fatcat.parallelwireless>
On Wed, Jan 20, 2016 at 06:57:27PM +0530, Anupam Kapoor wrote:
>
> >>>>> [2016-01-20T13:55:54+0530]: "Nicholas Mc Guire" (Nicholas):
> ,----[ Nicholas ]
> | that would still have the same limitation with resepct to time granuarlity
> | and as Documentation/timers/
> `----
> ah yes, that's true.
>
> ,----[ Nicholas ]
> | if you really need very short delays then you will need to resort to hrtimers
> | (and thus be to some extent config dependent) usleep_range(min, max) is the
> | prefered interface in that case.
> `----
> any specific reason why schedule_hrtimeout(...) cannot be used ?
>
It can, but same thing, unless you really need a very specific timeout
it is better to pass a range so that the kernel can consolidate the timeout
list - so the _range is a system level optimization.
so schedule_hrtimeout_range() would be prefered
<snip>
* The @delta argument gives the kernel the freedom to schedule the
* actual wakeup to a time that is both power and performance friendly.
* The kernel give the normal best effort behavior for "@expires+ at delta",
* but may decide to fire the timer earlier, but no earlier than @expires.
<snip>
and you need to convert the timeout to ktime e.g. with ms_to_ktime()
thx!
hofrat
prev parent reply other threads:[~2016-01-20 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 19:51 how to use wait_event_interruptible_timeout with less than 1 jiffie timeout? Daniel.
2016-01-20 6:20 ` Anupam Kapoor
2016-01-20 8:25 ` Nicholas Mc Guire
2016-01-20 13:27 ` Anupam Kapoor
2016-01-20 15:01 ` Nicholas Mc Guire [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=20160120150109.GC16707@osadl.at \
--to=der.herr@hofr.at \
--cc=kernelnewbies@lists.kernelnewbies.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 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.