Lines Matching refs:buffer

11 overhead  required  for  buffer  pool  management.    It   automatically
25 entire buffer pool.
29 * Quantisation of buffer sizes to a power of two to
70 buffer pools may not be larger than a segment, but since BGET allows any
71 number of separate buffer pools, there is no limit on the total storage
91 buffer allocation (often in a separate RAM address space distinct from
94 the buffer pool area in RAM, then allocate buffers with bget() and
105 Initially define a buffer pool of an appropriate size with
111 brel(). If a buffer allocation request fails, obtain more storage from
112 the underlying operating system, add it to the buffer pool by another
127 release storage as before. You can supply an initial buffer pool with
145 call requested a buffer larger than this; buffers larger than the
148 a pointer to the new block and BGET expands the buffer pool; if it
168 void bpool(void *buffer, bufsize len);
170 Create a buffer pool of <len> bytes, using the storage starting at
171 <buffer>. You can call bpool() subsequently to contribute additional
172 storage to the overall buffer pool.
176 Allocate a buffer of <size> bytes. The address of the buffer is
178 buffer.
182 Allocate a buffer of <size> bytes and clear it to all zeroes. The
183 address of the buffer is returned, or NULL if insufficient memory was
184 available to allocate the buffer.
186 void *bgetr(void *buffer, bufsize newsize);
188 Reallocate a buffer previously allocated by bget(), changing its size to
190 insufficient memory is available to reallocate the buffer, in which case
191 the original buffer remains intact.
195 Return the buffer <buf>, previously allocated by bget(), to the free
207 become empty. If <compact> is non-NULL, whenever a buffer allocation
209 specifying the number of bytes (total buffer size, including header
218 release any space or add storage to the buffer pool), the allocation
221 called, the state of the buffer allocator is identical to that at the
224 the buffer pool in any manner which would be valid were the application
228 example, a <compact> function that released a buffer in the process of
237 allocation will proceed using the expanded buffer pool. If <acquire>
243 buffer overhead) to be satisfied directly by calls to the <acquire>
276 The buffer pointed to by <buf> is dumped on standard output.
280 All buffers in the buffer pool <pool>, previously initialised by a call
287 The named buffer pool, previously initialised by a call on bpool(), is
297 how many buffer allocation attempts
307 buffers in a buffer pool. */
311 a buffer pool. */
316 or free buffer. */
320 the total free space in the buffer
322 buffer, and the total space