Now
MAIN commitmail json YAML
src/sys/dev/raidframe/rf_driver.c@1.123
/
diff
/
nxr@1.123
src/sys/dev/raidframe/rf_engine.c@1.42 / diff / nxr@1.42
src/sys/dev/raidframe/rf_netbsdkintf.c@1.285 / diff / nxr@1.285
src/sys/dev/raidframe/rf_paritymap.c@1.7 / diff / nxr@1.7
src/sys/dev/raidframe/rf_raid.h@1.39 / diff / nxr@1.39
src/sys/dev/raidframe/rf_states.c@1.45 / diff / nxr@1.45
src/sys/dev/raidframe/rf_engine.c@1.42 / diff / nxr@1.42
src/sys/dev/raidframe/rf_netbsdkintf.c@1.285 / diff / nxr@1.285
src/sys/dev/raidframe/rf_paritymap.c@1.7 / diff / nxr@1.7
src/sys/dev/raidframe/rf_raid.h@1.39 / diff / nxr@1.39
src/sys/dev/raidframe/rf_states.c@1.45 / diff / nxr@1.45
convert the iodone_lock to a mutex, and use a condvar for signalling.
this only handles the smallest use of old simple_lock/tsleep/wakeup
APIs inside raidframe, and it points out that cv(9)'s have only one
wait channel per cv, whereas each tsleep() caller can specify a
different wait channel. this change removes the difference between
normal raidio and waiting for IO during shutdown.
i've tested this one 3 systems, ran atf, and had mlelstv and rmind
review the change.
this only handles the smallest use of old simple_lock/tsleep/wakeup
APIs inside raidframe, and it points out that cv(9)'s have only one
wait channel per cv, whereas each tsleep() caller can specify a
different wait channel. this change removes the difference between
normal raidio and waiting for IO during shutdown.
i've tested this one 3 systems, ran atf, and had mlelstv and rmind
review the change.