| History log of /src/sys/dev/raidframe/rf_psstatus.h |
| Revision | | Date | Author | Comments |
| 1.16 |
| 23-Jul-2021 |
oster | Extensive mechanical changes to the pools used in RAIDframe.
Alloclist remains not per-RAID, so initialize that pool
separately/differently than the rest.
The remainder of pools in RF_Pools_s are now per-RAID pools. Mostly
mechanical changes to functions to allocate/destroy per-RAID pools.
Needed to make raidPtr available in certain cases to be able to find
the per-RAID pools.
Extend rf_pool_init() to now populate a per-RAID wchan value that is
unique to each pool for a given RAID device.
TODO: Complete the analysis of the minimum number of items that are
required for each pool to allow IO to progress (i.e. so that a request
for pool resources can always be satisfied), and dynamically scale
minimum pool sizes based on RAID configuration.
|
| 1.15 |
| 10-Oct-2019 |
christos | branches: 1.15.12;
fix the function pointer and callback mess:
- callback functions return 0 and their result is not checked; make them void.
- there are two types of callbacks and they used to overload their parameters
and the callback structure; separate them into "function" and "value"
callbacks.
- make the wait function signature consistent.
|
| 1.14 |
| 03-May-2011 |
mrg | branches: 1.14.56;
convert the pssTable mutex into a kmutex/cv.
|
| 1.13 |
| 14-Feb-2006 |
oster | branches: 1.13.92; 1.13.98;
RAIDframe was erroneously re-initializing the Parity Stripe Status
pool each time a new array was configured. This causes grief
with things like 'vmstat -m' by causing it to loop. Make RAIDframe
only initialize PSS bits once.
Pointed out by simonb@. Fix tested by simonb@. Thanks!
|
| 1.12 |
| 11-Dec-2005 |
christos | branches: 1.12.2; 1.12.4; 1.12.6;
merge ktrace-lwp.
|
| 1.11 |
| 27-Feb-2005 |
perry | branches: 1.11.2; 1.11.4; 1.11.12;
nuke trailing whitespace
|
| 1.10 |
| 09-Apr-2004 |
oster | branches: 1.10.4; 1.10.6;
We really should have a wakeup in RF_UNLOCK_PSS_MUTEX in case we have
a nap in RF_LOCK_PSS_MUTEX!
|
| 1.9 |
| 18-Mar-2004 |
oster | branches: 1.9.2;
Re-work the locking mechanisms for reconstruct and PSS structures
such that we don't actually hold a simplelock while we are doing
a pool_get(), but that we still effectively protecting critical code.
This should fix all of the outstanding LOCKDEBUG warnings related to
rebuilding RAID sets.
|
| 1.8 |
| 08-Mar-2004 |
oster | Move pss_pool to rf_pools. Will save a bit of extra memory at
run-time, and we can only do one reconstruction at a time anyway.
Nuke pss_issued_pool - move it to an internal structure in pss.
|
| 1.7 |
| 03-Mar-2004 |
oster | Cleanup function prototypes.
|
| 1.6 |
| 03-Mar-2004 |
oster | - cleanup memory allocation in rf_AllocPSStatus()
- change function signature of rf_LookupRUStatus(). The last argument
is now a pointer to a new PSS, in case one is needed. Rather than
having rf_LookupRUStatus() allocate a new PSS, we pre-allocate one
beforehand, where necessary, just in case.
- change callers of rf_lookupRUStatus() to deal with the new way of
calling rf_lookupRUStatus().
[no improvement or worsening of parity rebuild/initialization performance.]
|
| 1.5 |
| 29-Dec-2003 |
oster | [Having received a definite lack of strenuous objection, a small amount
of strenuous agreement, and some general agreement, this commit is
going ahead because it's now starting to block some other changes I
wish to make.]
Remove most of the support for the concept of "rows" from RAIDframe.
While the "row" interface has been exported to the world, RAIDframe
internals have really only supported a single row, even though they
have feigned support of multiple rows.
Nothing changes in configuration land -- config files still need to
specify a single row, etc. All auto-config structures remain fully
forward/backwards compatible.
The only visible difference to the average user should be a
reduction in the size of a GENERIC kernel (i386) by 4.5K. For those
of us trolling through RAIDframe kernel code, a lot of the driver
configuration code has become a LOT easier to read.
|
| 1.4 |
| 04-Oct-2001 |
oster | branches: 1.4.18;
Step 2 of the disentanglement. We now look to <dev/raidframe/*> for
the stuff that used to live in rf_types.h, rf_raidframe.h, rf_layout.h,
rf_netbsd.h, rf_raid.h, rf_decluster,h, and a few other places.
Believe it or not, when this is all done, things will be cleaner.
No functional changes to RAIDframe.
|
| 1.3 |
| 05-Feb-1999 |
oster | branches: 1.3.20; 1.3.22; 1.3.24;
Phase 2 of the RAIDframe cleanup. The source is now closer to KNF
and is much easier to read. No functionality changes.
|
| 1.2 |
| 26-Jan-1999 |
oster | RAIDframe cleanup, phase 1. Nuke simulator support, user-land driver,
out-dated comments, and other unneeded stuff. This helps prepare
for cleaning up the rest of the code, and adding new functionality.
No functional changes to the kernel code in this commit.
|
| 1.1 |
| 13-Nov-1998 |
oster | RAIDframe, version 1.1, from the Parallel Data Laboratory at
Carnegie Mellon University. Full RAID implementation, including
levels 0, 1, 4, 5, 6, parity logging, and a few other goodies.
Ported to NetBSD by Greg Oster.
|
| 1.3.24.1 |
| 11-Oct-2001 |
fvdl | Catch up with -current. Fix some bogons in the sparc64 kbd/ms
attach code. cd18xx conversion provided by mrg.
|
| 1.3.22.1 |
| 10-Jan-2002 |
thorpej | Sync kqueue branch with -current.
|
| 1.3.20.1 |
| 22-Oct-2001 |
nathanw | Catch up to -current.
|
| 1.4.18.4 |
| 04-Mar-2005 |
skrll | Sync with HEAD.
Hi Perry!
|
| 1.4.18.3 |
| 21-Sep-2004 |
skrll | Fix the sync with head I botched.
|
| 1.4.18.2 |
| 18-Sep-2004 |
skrll | Sync with HEAD.
|
| 1.4.18.1 |
| 03-Aug-2004 |
skrll | Sync with HEAD
|
| 1.9.2.1 |
| 09-Apr-2004 |
jmc | Pullup rev 1.10 (requested by oster in ticket #106)
We really should have a wakeup in RF_UNLOCK_PSS_MUTEX in case we have
a nap in RF_LOCK_PSS_MUTEX\!
|
| 1.10.6.1 |
| 19-Mar-2005 |
yamt | sync with head. xen and whitespace. xen part is not finished.
|
| 1.10.4.1 |
| 29-Apr-2005 |
kent | sync with -current
|
| 1.11.12.1 |
| 15-Feb-2006 |
riz | Pull up following revision(s) (requested by oster in ticket #1170):
sys/dev/raidframe/rf_driver.c: revision 1.110
sys/dev/raidframe/rf_psstatus.c: revision 1.31
sys/dev/raidframe/rf_psstatus.h: revision 1.13
RAIDframe was erroneously re-initializing the Parity Stripe Status
pool each time a new array was configured. This causes grief
with things like 'vmstat -m' by causing it to loop. Make RAIDframe
only initialize PSS bits once.
Pointed out by simonb@. Fix tested by simonb@. Thanks!
|
| 1.11.4.1 |
| 21-Jun-2006 |
yamt | sync with head.
|
| 1.11.2.1 |
| 15-Feb-2006 |
riz | Pull up following revision(s) (requested by oster in ticket #1170):
sys/dev/raidframe/rf_driver.c: revision 1.110
sys/dev/raidframe/rf_psstatus.c: revision 1.31
sys/dev/raidframe/rf_psstatus.h: revision 1.13
RAIDframe was erroneously re-initializing the Parity Stripe Status
pool each time a new array was configured. This causes grief
with things like 'vmstat -m' by causing it to loop. Make RAIDframe
only initialize PSS bits once.
Pointed out by simonb@. Fix tested by simonb@. Thanks!
|
| 1.12.6.1 |
| 22-Apr-2006 |
simonb | Sync with head.
|
| 1.12.4.1 |
| 09-Sep-2006 |
rpaulo | sync with head
|
| 1.12.2.1 |
| 18-Feb-2006 |
yamt | sync with head.
|
| 1.13.98.1 |
| 06-Jun-2011 |
jruoho | Sync with HEAD.
|
| 1.13.92.1 |
| 31-May-2011 |
rmind | sync with head
|
| 1.14.56.1 |
| 13-Apr-2020 |
martin | Mostly merge changes from HEAD upto 20200411
|
| 1.15.12.1 |
| 01-Aug-2021 |
thorpej | Sync with HEAD.
|
