diff options
| author | NeilBrown <[email protected]> | 2018-02-13 08:22:36 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2018-02-16 15:19:10 +0100 |
| commit | 98b092804497c53ed694257dacd08f0ecc133bc9 (patch) | |
| tree | 7057903d90e4c87aeabc1ef571889a716e03e3d5 /tools/perf/scripts/python | |
| parent | 672b63e55bdee71150e3cc472f6294e0535a95ad (diff) | |
staging: lustre: use wait_event_idle_timeout() where appropriate.
When the lwi arg has a timeout, but no timeout
callback function, l_wait_event() acts much the same as
wait_event_idle_timeout() - the wait is not interruptible and
simply waits for the event or the timeouts.
The most noticable difference is that the return value is
-ETIMEDOUT or 0, rather than 0 or non-zero.
Another difference is that if the timeout is zero, l_wait_event()
will not time out at all. In the one case where that is possible
we need to conditionally use wait_event_idle().
So replace all such calls with wait_event_idle_timeout(), being
careful of the return value.
In one case, there is no event expected, only the timeout
is needed. So use schedule_timeout_uninterruptible().
Note that the presence or absence of LWI_ON_SIGNAL_NOOP
has no effect in these cases. It only has effect if the timeout
callback is non-NULL, or the timeout is zero, or
LWI_TIMEOUT_INTR_ALL() is used.
Reviewed-by: James Simmons <[email protected]>
Signed-off-by: NeilBrown <[email protected]>
Reviewed-by: Patrick Farrell <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions