NetBSD/sys/dev/raidframe
oster b68ecaf95f Always ask for a new RF_StripeLockDesc_t "just in case", and then
give it back if we don't need it.  If we don't allocate it before
we take our lock, LOCKDEBUG (rightfully) complains that we're trying
to grab something from the pool with PR_WAITOK.  This code (and the
PR_WAITOK in particular) really needs to be revisited at some point.
2004-01-23 01:57:08 +00:00
..
files.raidframe The ugly wonderment of appropriately placed ASCII characters 2003-12-29 06:37:47 +00:00
Makefile
raidframeio.h
raidframevar.h As noted by Thierry Deval in a posting to misc/at/openbsd.org, 2004-01-04 06:37:16 +00:00
rf_acctrace.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_acctrace.h
rf_alloclist.c Replace the DO_FREE() macro with just RF_Free(). No functional changes, 2003-12-31 16:32:50 +00:00
rf_alloclist.h
rf_archs.h
rf_aselect.c Fix the "We panic if we can't create a DAG" problem that's existed 2004-01-02 21:41:08 +00:00
rf_aselect.h
rf_callback.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_callback.h
rf_chaindecluster.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_chaindecluster.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_copyback.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_copyback.h Nuke a few more 'row'-related bits that were missed in the row-removal. 2004-01-01 19:32:55 +00:00
rf_cvscan.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_cvscan.h
rf_dag.h
rf_dagdegrd.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_dagdegrd.h
rf_dagdegwr.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_dagdegwr.h
rf_dagffrd.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_dagffrd.h
rf_dagffwr.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_dagffwr.h
rf_dagflags.h Cleanup some unused desc->flags: 2004-01-01 23:35:08 +00:00
rf_dagfuncs.c Since the LOCK and UNLOCK flags are never used, no need in extracting them. 2004-01-10 17:04:44 +00:00
rf_dagfuncs.h Since the LOCK and UNLOCK flags are never used, no need in extracting them. 2004-01-10 17:04:44 +00:00
rf_dagutils.c Since the LOCK and UNLOCK flags are never used, no need in extracting them. 2004-01-10 17:04:44 +00:00
rf_dagutils.h
rf_debugMem.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_debugMem.h - first kick at a major reworking of RAIDframe's memory allocation code: 2003-12-29 03:33:47 +00:00
rf_debugprint.c Tidy up the #includes a bit. 2004-01-01 19:37:17 +00:00
rf_debugprint.h
rf_decluster.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_decluster.h
rf_declusterPQ.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_declusterPQ.h
rf_desc.h Nuke a bunch of unused variables: 2004-01-01 19:27:35 +00:00
rf_diskqueue.c Nuke a bunch of unused variables: 2004-01-01 19:27:35 +00:00
rf_diskqueue.h Nuke a bunch of unused variables: 2004-01-01 19:27:35 +00:00
rf_disks.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_disks.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_driver.c Add missing simple_lock_init(). Noted by skrueger-at-europe-dot-com. 2004-01-15 20:27:27 +00:00
rf_driver.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_engine.c Fix the "We panic if we can't create a DAG" problem that's existed 2004-01-02 21:41:08 +00:00
rf_engine.h
rf_etimer.h
rf_evenodd_dagfuncs.c [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_evenodd_dagfuncs.h
rf_evenodd_dags.c
rf_evenodd_dags.h
rf_evenodd.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_evenodd.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_fifo.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_fifo.h
rf_general.h Finally cleanup RF_BZERO. Turns out that 'bp' was only used to obtain 2004-01-01 20:39:58 +00:00
rf_geniq.c
rf_hist.h
rf_interdecluster.c
rf_interdecluster.h
rf_invertq.c
rf_invertq.h
rf_kintf.h
rf_layout.c As noted by Thierry Deval in a posting to misc/at/openbsd.org, 2004-01-04 06:37:16 +00:00
rf_layout.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_map.c No point keeping 'pt' around. It's only ever assigned to. 2003-12-30 22:12:10 +00:00
rf_map.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_mcpair.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_mcpair.h
rf_netbsd.h
rf_netbsdkintf.c store a i/o priority hint in struct buf for buffer queue discipline. 2004-01-10 14:39:50 +00:00
rf_nwayxor.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_nwayxor.h
rf_options.c
rf_options.h
rf_optnames.h Cleanup rf_enableAtomicRMW and its use. According to the comments, we 2004-01-09 23:26:17 +00:00
rf_paritylog.c
rf_paritylog.h
rf_paritylogDiskMgr.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_paritylogDiskMgr.h
rf_paritylogging.c _rf_create_managed_cond() is now left doing nothing. Convert callers. 2003-12-29 05:48:13 +00:00
rf_paritylogging.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_parityloggingdags.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_parityloggingdags.h
rf_parityscan.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_parityscan.h
rf_pq.c
rf_pq.h
rf_pqdeg.c
rf_pqdeg.h
rf_pqdegdags.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_pqdegdags.h
rf_psstatus.c Increase the scope of RF_DEBUG_PSS to cover a bit more stuff. 2003-12-31 00:42:46 +00:00
rf_psstatus.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid0.c Fix the "We panic if we can't create a DAG" problem that's existed 2004-01-02 21:41:08 +00:00
rf_raid0.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid1.c iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_raid1.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid4.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_raid4.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid5_rotatedspare.c [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid5_rotatedspare.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid5.c Fix the "We panic if we can't create a DAG" problem that's existed 2004-01-02 21:41:08 +00:00
rf_raid5.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_raid.h iCleanup the RF_CREATE_PARAM3(). Middle two "arguments" were nothing 2004-01-10 00:56:27 +00:00
rf_reconbuffer.c Remove "row" from DEBUG statements. 2004-01-02 11:52:15 +00:00
rf_reconbuffer.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_reconmap.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_reconmap.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_reconstruct.c raidPtr->reconControl->percentCompleted only gets used in one 2004-01-04 21:06:04 +00:00
rf_reconstruct.h Nuke a few more 'row'-related bits that were missed in the row-removal. 2004-01-01 19:32:55 +00:00
rf_reconutil.c Nuke a bunch of unused variables: 2004-01-01 19:27:35 +00:00
rf_reconutil.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_revent.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_revent.h [Having received a definite lack of strenuous objection, a small amount 2003-12-29 02:38:17 +00:00
rf_shutdown.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_shutdown.h
rf_sstf.c - first kick at a major reworking of RAIDframe's memory allocation code: 2003-12-29 03:33:47 +00:00
rf_sstf.h
rf_states.c Fix the "We panic if we can't create a DAG" problem that's existed 2004-01-02 21:41:08 +00:00
rf_states.h
rf_stripelocks.c Always ask for a new RF_StripeLockDesc_t "just in case", and then 2004-01-23 01:57:08 +00:00
rf_stripelocks.h
rf_strutils.c
rf_threadstuff.h rf_lkmgr_mutex_init() is only called from one spot, and it really 2003-12-29 06:30:42 +00:00
rf_utils.c Some days you wonder if some of the function declaration consistency 2003-12-30 21:59:03 +00:00
rf_utils.h