diff options
author | Chris Dunlap <[email protected]> | 2014-02-12 10:30:18 -0800 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2014-03-31 16:11:21 -0700 |
commit | 8c7aa0cfc47578d1d38f80ecb7c66eed7cde5c59 (patch) | |
tree | 3f4f8ec16357c89941b544adcd7009a57d0e4893 /cmd/zed/zed.d | |
parent | 07917db9908516aa3fd55d39d2c1792aca8bebcd (diff) |
Replace zpool_events_next() "block" parm w/ "flags"
zpool_events_next() can be called in blocking mode by specifying a
non-zero value for the "block" parameter. However, the design of
the ZFS Event Daemon (zed) requires additional functionality from
zpool_events_next(). Instead of adding additional arguments to the
function, it makes more sense to use flags that can be bitwise-or'd
together.
This commit replaces the zpool_events_next() int "block" parameter with
an unsigned bitwise "flags" parameter. It also defines ZEVENT_NONE
to specify the default behavior. Since non-blocking mode can be
specified with the existing ZEVENT_NONBLOCK flag, the default behavior
becomes blocking mode. This, in effect, inverts the previous use
of the "block" parameter. Existing callers of zpool_events_next()
have been modified to check for the ZEVENT_NONBLOCK flag.
Signed-off-by: Chris Dunlap <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Issue #2
Diffstat (limited to 'cmd/zed/zed.d')
0 files changed, 0 insertions, 0 deletions