From: anupam.kapoor@gmail.com (Anupam Kapoor)
To: kernelnewbies@lists.kernelnewbies.org
Subject: how to use wait_event_interruptible_timeout with less than 1 jiffie timeout?
Date: Wed, 20 Jan 2016 18:57:27 +0530 [thread overview]
Message-ID: <87a8o0s7nk.fsf@fatcat.parallelwireless> (raw)
In-Reply-To: <20160120082554.GE13776@osadl.at>
>>>>> [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 ?
--
kind regards
anupam
next prev parent reply other threads:[~2016-01-20 13:27 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 [this message]
2016-01-20 15:01 ` Nicholas Mc Guire
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=87a8o0s7nk.fsf@fatcat.parallelwireless \
--to=anupam.kapoor@gmail.com \
--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 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).