summaryrefslogtreecommitdiff
path: root/sys/dev/microcode/run/microcode.h
diff options
context:
space:
mode:
Diffstat (limited to 'sys/dev/microcode/run/microcode.h')
0 files changed, 0 insertions, 0 deletions
.c?id=f9496794ff5670818d14b58cb9ffda8f702eaed7'>- Change the allocation macros to be more like function callschristos - Change sizeof(type) -> sizeof(*variable) - Use macros for the long buffer length allocations - Remove "bit polishing" memsets() -- do them only once - Remove unnecessary casts Thanks to oster@ for finding bugs and testing. 2011-05-03convert the pssTable mutex into a kmutex/cv.mrg 2006-11-16__unused removal on arguments; approved by core.christos 2006-10-12- sprinkle __unused on function decls.christos - fix a couple of unused bugs - no more -Wno-unused for i386 2006-02-14RAIDframe was erroneously re-initializing the Parity Stripe Statusoster 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! 2005-12-11merge ktrace-lwp.christos 2005-02-27nuke trailing whitespaceperry 2004-03-18Re-work the locking mechanisms for reconstruct and PSS structuresoster 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. 2004-03-08Move pss_pool to rf_pools. Will save a bit of extra memory atoster 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. 2004-03-07- Introduce rf_pools which contains all of the various global pools usedoster by RAIDframe. Convert all other RAIDframe global pools to use pools defined within this new structure. - Introduce rf_pool_init(), used for initializing a single pool in RAIDframe. Teach each of the configuration routines to use rf_pool_init(). - Cleanup a few pool-related comments. - Cleanup revent initialization and #defines. - Add a missing pool_destroy() for the reconbuffer pool. (Saves another 1K off of an i386 GENERIC kernel, and makes stuff a lot more readable) 2004-03-05- remove the RF_*_INC's, as necessary. They are not needed any more.oster - introduce RF_MIN_*'s, as necessary. These will indicate the low-water mark for pools as well as the pool_prime() value. - add pool_setlowat() for the critical pools. - pool_prime() and pool_setlowat() the raidframe_cbufpool. - re-order some pool_prime()'s and pool_sethiwat()'s for clarity. 2004-03-04Remove a comment that is no longer relevant.oster 2004-03-03Improve comments on rf_LookupRUStatus(). No functional changes.oster 2004-03-03- cleanup memory allocation in rf_AllocPSStatus()oster - 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.] 2004-02-29Adjust _rf_ShutdownCreate() so that it is willing to wait for moreoster memory. Since we only now ever "return(0)", just return (void) instead. Cleanup all uses of rf_ShutdownCreate() to not worry about it ever failing. Shaves another 600 bytes off of an i386 GENERIC kernel. 2003-12-31Increase the scope of RF_DEBUG_PSS to cover a bit more stuff.oster 2003-12-30Some days you wonder if some of the function declaration consistencyoster was just an accident in the first place. Cleanup function decls and a few comments. [ok.. so I wasn't going to fix this many.. but once you're on a roll....] 2003-12-29Since rf_mutex_destroy() is effectively a NOP now, nuke it.oster 2003-12-29Simplify defn's of rf_mutex_init() and rf_mutex_destroy(). Sinceoster 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! 2003-12-29- first kick at a major reworking of RAIDframe's memory allocation code:oster - 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. 2003-12-29[Having received a definite lack of strenuous objection, a small amountoster 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. 2003-12-21Since the 5th arg of pool_init() wasn't actually the numberoster of items with which to prime the pool, we now prime each pool using pool_prime(). 2003-12-21Fix usage of fifth argument to pool_init().simonb 2002-11-12xorBufCount needs to be initialized too!oster 2002-10-11poolify the allocation of Parity Stripe Status structures.oster XXX: Current code may have problems if kernel memory is completely depleted. This is, unfortunately, not the only chunk of RAIDframe code to have this problem, and will have to be dealt with. :( 2002-09-19Introduce and use RF_DEBUG_PSS, and save a few more bytes.oster 2002-09-14Everyone and their dog was using RF_ERRORMSG3 to print out the sameoster sort of error message, over and over again, in different files. Rather than having the same text repeated in multiple .o files, create a couple of little functions to do the printing, and save a bundle of space. Also improves readability of code. 2001-11-13add RCSIDslukem 2001-10-04Step 2 of the disentanglement. We now look to <dev/raidframe/*> foroster 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. 2001-07-18bzero -> memsetthorpej