| Age | Commit message (Collapse) | Author |
|
|
|
neither of these ever fail, no need to have a return value. That
makes all the "error detection" on these functions completely
unneeded. But since we're here, if we don't have a return value, then
why not make these macros? My.. look how things keep shrinking, with
no loss in functionality!
|
|
removes useless error detection, and generally makes things easier to follow.
|
|
|
|
clean_rad() were -- these days they only serve to clutter things up.
Remove the functions, and put the 2 lines of actual useful initialization
into rf_AllocMCPair().
|
|
to make things look far more complicated than they really are. It was
also impossible for any of the mutex/cond initializations in
init_rad() to actually fail, making the "error detection code"
unneeded. Collapse the little work done by init_rad into
rf_AllocRaidAccDesc(), and nuke init_rad() and clean_rad(). Save
another 0.25K in GENERIC.
[To be accurate/complete, init_rad() and clean_rad() *ARE* used in the
simulator version of RAIDframe. But we're so far removed from that
now that there is no point pretending otherwise.]
|
|
|
|
|
|
- all freelists converted to pools
- initialization of structure members in certain cases where
code was relying on specific allocation and usage properties
to keep structures in a "known state" (that doesn't work with
pools!).
- make most pool_get() be "PR_WAITOK" until they can be analyzed
further, and/or have proper error handling added.
- all RF_Mallocs zero the space returned, so there is no difference
between RF_Calloc and RF_Malloc. In fact, all the RF_Calloc()'s
do is tend to do is get things horribly confused.
Make RF_Malloc() the "general memory allocator", with
RF_MallocAndAdd() the "general memory allocator with
allocation list".
- some of these RF_Malloc's et al. are destined to disappear.
- remove rf_rdp_freelist entirely (it's not used anywhere!)
- remove: #include "rf_freelist.h"
- to the files that were relying on the above, add: #include "rf_general.h"
- add: #include "rf_debugMem.h" to rf_shutdown.h to make it happy
about the loss of: #include "rf_freelist.h".
This shrinks an i386 GENERIC kernel by approx 5K. RAIDframe now
weighs in at about 162K on i386.
|
|
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.
|
|
completeness)
If we don't have enough memory to allocate the pda freelist, make sure to
cleanup the asm freelist.
|
|
of items with which to prime the pool, we now prime each
pool using pool_prime().
|
|
|
|
to infoFunc.
|
|
|
|
|
|
|
|
|
|
|
|
Patches provided by Joel Baker in PR 22364, verified by myself.
|
|
|
|
- alist_mutex is a holdover from the simulator days, and it
wasn't even used back then. Toss the variable and init/destroy calls.
|
|
|
|
|
|
|
|
and need to be examined and discussed more.
|
|
be inserted into ktrace records. The general change has been to replace
"struct proc *" with "struct lwp *" in various function prototypes, pass
the lwp through and use l_proc to get the process pointer when needed.
Bump the kernel rev up to 1.6V
|
|
|
|
rather than the label itself. This paves the way for some future changes.
|
|
I hope I've found all the correct places!
|
|
as a hot spare. Closes PR#20989 by David Brownlee.
|
|
|
|
rf_stripelocks.c - make them static functions.
|
|
|
|
|
|
and VOP_ADVLOCK, delete casts from callers (and some to copyin/out).
|
|
use it. This fixes a few places where either b_dep or b_interlock were
not properly initialized.
|
|
|
|
|
|
difficult to read and understand. Most manuals of English style
therefore say that you should use "use".
|
|
|
|
malloc types into a structure, a pointer to which is passed around,
instead of an int constant. Allow the limit to be adjusted when the
malloc type is defined, or with a function call, as suggested by
Jonathan Stone.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
out in the rest. Thanks to Krister!
|