Blame view
Documentation/flexible-arrays.txt
5.6 KB
af7175bc2 flexible-arrays.t... |
1 |
=================================== |
6c19efb46 Document the flex... |
2 |
Using flexible arrays in the kernel |
af7175bc2 flexible-arrays.t... |
3 4 5 6 |
=================================== :Updated: Last updated for 2.6.32 :Author: Jonathan Corbet <corbet@lwn.net> |
6c19efb46 Document the flex... |
7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 |
Large contiguous memory allocations can be unreliable in the Linux kernel. Kernel programmers will sometimes respond to this problem by allocating pages with vmalloc(). This solution not ideal, though. On 32-bit systems, memory from vmalloc() must be mapped into a relatively small address space; it's easy to run out. On SMP systems, the page table changes required by vmalloc() allocations can require expensive cross-processor interrupts on all CPUs. And, on all systems, use of space in the vmalloc() range increases pressure on the translation lookaside buffer (TLB), reducing the performance of the system. In many cases, the need for memory from vmalloc() can be eliminated by piecing together an array from smaller parts; the flexible array library exists to make this task easier. A flexible array holds an arbitrary (within limits) number of fixed-sized objects, accessed via an integer index. Sparse arrays are handled reasonably well. Only single-page allocations are made, so memory allocation failures should be relatively rare. The down sides are that the arrays cannot be indexed directly, individual object size cannot exceed the system page size, and putting data into a flexible array requires a copy operation. It's also worth noting that flexible arrays do no internal locking at all; if concurrent access to an array is possible, then the caller must arrange for appropriate mutual exclusion. |
af7175bc2 flexible-arrays.t... |
31 |
The creation of a flexible array is done with:: |
6c19efb46 Document the flex... |
32 33 34 35 36 37 38 39 40 41 42 43 |
#include <linux/flex_array.h> struct flex_array *flex_array_alloc(int element_size, unsigned int total, gfp_t flags); The individual object size is provided by element_size, while total is the maximum number of objects which can be stored in the array. The flags argument is passed directly to the internal memory allocation calls. With the current code, using flags to ask for high memory is likely to lead to notably unpleasant side effects. |
af7175bc2 flexible-arrays.t... |
44 |
It is also possible to define flexible arrays at compile time with:: |
1243ba98e Update flex_array... |
45 46 47 48 49 |
DEFINE_FLEX_ARRAY(name, element_size, total); This macro will result in a definition of an array with the given name; the element size and total will be checked for validity at compile time. |
af7175bc2 flexible-arrays.t... |
50 |
Storing data into a flexible array is accomplished with a call to:: |
6c19efb46 Document the flex... |
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 |
int flex_array_put(struct flex_array *array, unsigned int element_nr, void *src, gfp_t flags); This call will copy the data from src into the array, in the position indicated by element_nr (which must be less than the maximum specified when the array was created). If any memory allocations must be performed, flags will be used. The return value is zero on success, a negative error code otherwise. There might possibly be a need to store data into a flexible array while running in some sort of atomic context; in this situation, sleeping in the memory allocator would be a bad thing. That can be avoided by using GFP_ATOMIC for the flags value, but, often, there is a better way. The trick is to ensure that any needed memory allocations are done before |
af7175bc2 flexible-arrays.t... |
66 |
entering atomic context, using:: |
6c19efb46 Document the flex... |
67 68 |
int flex_array_prealloc(struct flex_array *array, unsigned int start, |
5d30b10bd flex_array: flex_... |
69 |
unsigned int nr_elements, gfp_t flags); |
6c19efb46 Document the flex... |
70 71 |
This function will ensure that memory for the elements indexed in the range |
5d30b10bd flex_array: flex_... |
72 |
defined by start and nr_elements has been allocated. Thereafter, a |
6c19efb46 Document the flex... |
73 74 |
flex_array_put() call on an element in that range is guaranteed not to block. |
af7175bc2 flexible-arrays.t... |
75 |
Getting data back out of the array is done with:: |
6c19efb46 Document the flex... |
76 77 78 79 80 81 82 83 84 |
void *flex_array_get(struct flex_array *fa, unsigned int element_nr); The return value is a pointer to the data element, or NULL if that particular element has never been allocated. Note that it is possible to get back a valid pointer for an element which has never been stored in the array. Memory for array elements is allocated one page at a time; a single allocation could provide memory for several |
1243ba98e Update flex_array... |
85 86 87 88 89 |
adjacent elements. Flexible array elements are normally initialized to the value FLEX_ARRAY_FREE (defined as 0x6c in <linux/poison.h>), so errors involving that number probably result from use of unstored array entries. Note that, if array elements are allocated with __GFP_ZERO, they will be initialized to zero and this poisoning will not happen. |
af7175bc2 flexible-arrays.t... |
90 |
Individual elements in the array can be cleared with:: |
1243ba98e Update flex_array... |
91 92 93 94 95 96 97 |
int flex_array_clear(struct flex_array *array, unsigned int element_nr); This function will set the given element to FLEX_ARRAY_FREE and return zero. If storage for the indicated element is not allocated for the array, flex_array_clear() will return -EINVAL instead. Note that clearing an element does not release the storage associated with it; to reduce the |
af7175bc2 flexible-arrays.t... |
98 |
allocated size of an array, call:: |
1243ba98e Update flex_array... |
99 100 101 102 103 104 105 |
int flex_array_shrink(struct flex_array *array); The return value will be the number of pages of memory actually freed. This function works by scanning the array for pages containing nothing but FLEX_ARRAY_FREE bytes, so (1) it can be expensive, and (2) it will not work if the array's pages are allocated with __GFP_ZERO. |
af7175bc2 flexible-arrays.t... |
106 |
It is possible to remove all elements of an array with a call to:: |
6c19efb46 Document the flex... |
107 108 109 110 |
void flex_array_free_parts(struct flex_array *array); This call frees all elements, but leaves the array itself in place. |
af7175bc2 flexible-arrays.t... |
111 |
Freeing the entire array is done with:: |
6c19efb46 Document the flex... |
112 113 114 115 116 117 |
void flex_array_free(struct flex_array *array); As of this writing, there are no users of flexible arrays in the mainline kernel. The functions described here are also not exported to modules; that will probably be fixed when somebody comes up with a need for it. |