Lines Matching full:function
102 If the C library malloc() function is too slow, not present in your
124 doesn't make much sense to provide a release function without an
125 acquisition function, does it?). Once the call-back functions have been
130 compaction function has been supplied. If so, it is called (with the
133 looping). If the compaction function is able to free any storage (it
136 if it fails again, call the compaction function again with the
139 If the compaction function returns zero, indicating failure to free
140 space, or no compaction function is defined, BGET next tests whether a
141 non-NULL allocation function was supplied to bectl(). If so, that
142 function is called with an argument indicating how many bytes of
147 If the allocation function succeeds in obtaining the storage, it returns
150 a non-NULL release function is supplied, expansion blocks which become
152 addresses to the release function.
162 BGET FUNCTION DESCRIPTIONS
208 request fails, the <compact> function will be called with arguments
214 increments on subsequent calls, permitting the <compact> function to
216 the <compact> function returns a nonzero value, the allocation attempt
220 <acquire> argument is non-NULL. At the time the <compact> function is
223 function may call brel(), bpool(), bstats(), and/or directly manipulate
225 in control. This does not, however, relieve the <compact> function of
228 example, a <compact> function that released a buffer in the process of
234 If <acquire> is non-NULL, that function will be called whenever an
235 allocation request fails. If the <acquire> function succeeds in
240 expansion block size. Providing an <acquire> function will cause
244 function. Automatic release of empty pool blocks will occur only if all
306 bpoold() function which dumps the
310 bpoolv() function for validating
314 bufdump() function which allows
319 bstats() function which calculates
337 bectl() function for automatic