File: alignment.html

package info (click to toggle)
boost 1.27.0-3
  • links: PTS
  • area: main
  • in suites: woody
  • size: 19,908 kB
  • ctags: 26,546
  • sloc: cpp: 122,225; ansic: 10,956; python: 4,412; sh: 855; yacc: 803; makefile: 257; perl: 165; lex: 90; csh: 6
file content (383 lines) | stat: -rw-r--r-- 23,636 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 
<HTML>
<HEAD>
<TITLE>Guaranteeing Alignment</TITLE>
<LINK HREF="../pool.css" REL="stylesheet" TYPE="text/css">
</HEAD>
<BODY>

<IMG SRC="../../../../c++boost.gif" WIDTH=276 HEIGHT=86 ALT="C++ Boost">

<H1 ALIGN=CENTER>Guaranteeing Alignment</H1>

<P>
<H2>Terminology</H2>

<P>
Review the <A HREF="../concepts.html">concepts document</A> if you are not already familiar with it.  Remember that <EM>block</EM> is a contiguous section of memory, which is <EM>partitioned</EM> or <EM>segregated</EM> into fixed-size <EM>chunks</EM>.  These <EM>chunks</EM> are what are allocated and deallocated by the user.

<P>
<H2>Overview</H2>

<P>
Each <SPAN CLASS="code">Pool</SPAN> has a single free list that can extend over a number of memory blocks.  Thus, <SPAN CLASS="code">Pool</SPAN> also has a linked list of allocated memory blocks.  Each memory block, by default, is allocated using <SPAN CLASS="code">new[]</SPAN>, and all memory blocks are freed on destruction.  It is the use of <SPAN CLASS="code">new[]</SPAN> that allows us to guarantee alignment.

<P>
<H2>Proof of Concept: Guaranteeing Alignment</H2>

<P>
Each block of memory is allocated as a POD type (specifically, an array of characters) through <SPAN CLASS="code">operator new[]</SPAN>.  Let <EM>POD_size</EM> be the number of characters allocated.

<P>
<H3>Predicate 1: Arrays may not have padding</H3>

<P>
This follows from the following quote:

<P>
[5.3.3/2] (Expressions::Unary expressions::Sizeof) &quot;... When applied to an array, the result is the total number of bytes in the array.  This implies that the size of an array of <EM>n</EM> elements is <EM>n</EM> times the size of an element.&quot;

<P>
Therefore, arrays cannot contain padding, though the elements within the arrays may contain padding.

<P>
<H3>Predicate 2: Any block of memory allocated as an array of characters through <SPAN CLASS="code">operator new[]</SPAN> (hereafter referred to as <EM>the block</EM>) is properly aligned for any object of that size or smaller</H3>

<P>
This follows from:

<UL>
<LI>[3.7.3.1/2] (Basic concepts::Storage duration::Dynamic storage duration::Allocation functions) &quot;... The pointer returned shall be suitably aligned so that it can be converted to a pointer of any complete object type and then used to access the object or array in the storage allocated ...&quot;</LI>
<LI>[5.3.4/10] (Expressions::Unary expressions::New) &quot;... For arrays of <SPAN CLASS="code">char</SPAN> and <SPAN CLASS="code">unsigned char</SPAN>, the difference between the result of the <EM>new-expression</EM> and the address returned by the allocation function shall be an integral multiple of the most stringent alignment requirement (3.9) of any object type whose size is no greater than the size of the array being created.  [<EM>Note:</EM> Because allocation functions are assumed to return pointers to storage that is appropriately aligned for objects of any type, this constraint on array allocation overhead permits the common idiom of allocating character arrays into which objects of other types will later be placed. ]&quot;</LI>
</UL>

<P>
<H3>Consider: imaginary object type <EM>Element</EM> of a size which is a multiple of some actual object size; assume sizeof(Element) &gt; POD_size</H3>

<P>
Note that an object of that size <EM>can</EM> exist.  One object of that size is an array of the &quot;actual&quot; objects.

<P>
Note that the block is properly aligned for an Element.  This directly follows from Predicate 2.

<P>
<H3>Corollary 1: The block is properly aligned for an array of Elements</H3>

<P>
This follows from Predicates 1 and 2, and the following quote:

<P>
[3.9/9] (Basic concepts::Types) &quot;An <EM>object type</EM> is a (possibly cv-qualified) type that is not a function type, not a reference type, and not a void type.&quot;  (Specifically, array types are object types.)

<P>
<H3>Corollary 2: For any pointer <EM>p</EM> and integer <EM>i</EM>, if p is properly aligned for the type it points to, then p + i (when well-defined) is properly aligned for that type; in other words, if an array is properly aligned, then each element in that array is properly aligned</H3>

<P>
There are no quotes from the Standard to directly support this argument, but it fits the common conception of the meaning of &quot;alignment&quot;.

<P>
Note that the conditions for p + i being well-defined are outlined in [5.7/5].  We do not quote that here, but only make note that it is well-defined if p and p + i both point into or one past the same array.

<P>
<H3>Let: sizeof(Element) be the least common multiple of sizes of several actual objects (T<SUB>1</SUB>, T<SUB>2</SUB>, T<SUB>3</SUB>, ...)</H3>

<P>
<H3>Let: <EM>block</EM> be a pointer to the memory block, <EM>pe</EM> be (Element *) block, and <EM>p<SUB>n</SUB></EM> be (T<SUB>n</SUB> *) block</H3>

<P>
<H3>Corollary 3: For each integer <EM>i</EM>, such that pe + i is well-defined, then for each <EM>n</EM>, there exists some integer <EM>j<SUB>n</SUB></EM> such that p<SUB>n</SUB> + j<SUB>n</SUB> is well-defined and refers to the same memory address as pe + i</H3>

<P>
This follows naturally, since the memory block is an array of Elements, and for each n, sizeof(Element) % sizeof(T<SUB>n</SUB>) == 0; thus, the boundary of each element in the array of Elements is also a boundary of each element in each array of T<SUB>n</SUB>.

<P>
<H3>Theorem: For each integer <EM>i</EM>, such that pe + i is well-defined, that address (pe + i) is properly aligned for each type T<SUB>n</SUB></H3>

<P>
Since pe + i is well-defined, then by Corollary 3, p<SUB>n</SUB> + j<SUB>n</SUB> is well-defined.  It is properly aligned from Predicate 2 and Corollaries 1 and 2.

<P>
<H2>Use of the Theorem</H2>

<P>
The proof above covers alignment requirements for cutting chunks out of a block.  The implementation uses actual object sizes of:

<UL>
<LI>The requested object size (requested_size); this is the size of chunks requested by the user</LI>
<LI>void * (pointer to void); this is because we interleave our free list through the chunks</LI>
<LI>size_type; this is because we store the size of the next block within each memory block</LI>
</UL>

<P>
Each block also contains a pointer to the next block; but that is stored as a pointer to void and cast when necessary, to simplify alignment requirements to the three types above.

<P>
Therefore, <SPAN CLASS="code">alloc_size</SPAN> is defined to be the lcm of the sizes of the three types above.

<P>
<H2>A Look at the Memory Block</H2>

<P>
Each memory block consists of three main sections.  The first section is the part that chunks are cut out of, and contains the interleaved free list.  The second section is the pointer to the next block, and the third section is the size of the next block.

<P>
Each of these sections may contain padding as necessary to guarantee alignment for each of the next sections.  The size of the first section is number_of_chunks * lcm(requested_size, sizeof(void *), sizeof(size_type)); the size of the second section is lcm(sizeof(void *), sizeof(size_type); and the size of the third section is sizeof(size_type).

<P>
Here's an example memory block, where requested_size == sizeof(void *) == sizeof(size_type) == 4:

<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="3" STYLE="clear: both;" ALIGN=CENTER>
<CAPTION><EM>Memory block containing 4 chunks, showing overlying array structures; FLP = Interleaved Free List Pointer</EM></CAPTION>

<TR><TH>Sections<TH>size_type alignment<TH>void * alignment<TH>requested_size alignment

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process

<TR><TD STYLE="background-color: gray; text-align: center;" ROWSPAN="4">Chunks section (16 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 1 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Chunk 1 (4 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">FLP for Chunk 2 (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Chunk 2 (4 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 3 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Chunk 3 (4 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">FLP for Chunk 4 (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Chunk 4 (4 bytes)

<TR><TD STYLE="background-color: silver; text-align: center;">Pointer to next Block (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Pointer to next Block (4 bytes)

<TR><TD STYLE="background-color: gray; text-align: center;">Size of next Block (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Size of next Block (4 bytes)

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process
</TABLE>

<P>
To show a visual example of possible padding, here's an example memory block where requested_size == 8 and sizeof(void *) == sizeof(size_type) == 4:

<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="3" STYLE="clear: both;" ALIGN=CENTER>
<CAPTION><EM>Memory block containing 4 chunks, showing overlying array structures; FLP = Interleaved Free List Pointer</EM></CAPTION>

<TR><TH>Sections<TH>size_type alignment<TH>void * alignment<TH>requested_size alignment

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process

<TR><TD STYLE="background-color: gray; text-align: center;" ROWSPAN="8">Chunks section (32 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 1 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="2">Chunk 1 (8 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">(4 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 2 (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="2">Chunk 2 (8 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">(4 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 3 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="2">Chunk 3 (8 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">(4 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP for Chunk 4 (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="2">Chunk 4 (8 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">(4 bytes)

<TR><TD STYLE="background-color: silver; text-align: center;">Pointer to next Block (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Pointer to next Block (4 bytes)

<TR><TD STYLE="background-color: gray; text-align: center;">Size of next Block (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Size of next Block (4 bytes)

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process
</TABLE>

<P>
Finally, here is a convoluted example where the requested_size is 7, sizeof(void *) == 3, and sizeof(size_type) == 5, showing how the least common multiple guarantees alignment requirements even in the oddest of circumstances:

<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="3" STYLE="clear: both;" ALIGN=CENTER>
<CAPTION><EM>Memory block containing 2 chunks, showing overlying array structures</EM></CAPTION>

<TR><TH>Sections<TH>size_type alignment<TH>void * alignment<TH>requested_size alignment

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process

<!-- First Section -->

<TR><TD STYLE="background-color: gray; text-align: center;" ROWSPAN="42">Chunks section (210 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">Interleaved free list pointer for Chunk 1 (15 bytes; 3 used)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="21">Chunk 1 (105 bytes; 7 used)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">Interleaved free list pointer for Chunk 2 (15 bytes; 3 used)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="21">Chunk 2 (105 bytes; 7 used)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
 <TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">(15 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)

<!-- Second Section -->

<TR><TD STYLE="background-color: silver; text-align: center;" ROWSPAN="3">Pointer to next Block (15 bytes; 3 used)
 <TD STYLE="background-color: gray; text-align: center;">(5 bytes)
 <TD STYLE="background-color: gray; text-align: center;" ROWSPAN="3">Pointer to next Block (15 bytes; 3 used)
<TR><TD STYLE="background-color: silver; text-align: center;">(5 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(5 bytes)

<!-- Third Section -->

<TR><TD STYLE="background-color: gray; text-align: center;">Size of next Block (5 bytes; 5 used)
 <TD STYLE="background-color: silver; text-align: center;">Size of next Block (5 bytes; 5 used)

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process
</TABLE>

<P>
<H2>How Contiguous Chunks are Handled</H2>

<P>
The theorem above guarantees all alignment requirements for allocating chunks and also implementation details such as the interleaved free list.  However, it does so by adding padding when necessary; therefore, we have to treat allocations of contiguous chunks in a different way.

<P>
Using array arguments similar to the above, we can translate any request for contiguous memory for <EM>n</EM> objects of requested_size into a request for <EM>m</EM> contiguous chunks.  <EM>m</EM> is simply ceil(n * requested_size / alloc_size), where alloc_size is the actual size of the chunks.  To illustrate:

<P>
Here's an example memory block, where requested_size == 1 and sizeof(void *) == sizeof(size_type) == 4:

<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="3" STYLE="clear: both;" ALIGN=CENTER>
<CAPTION><EM>Memory block containing 4 chunks; requested_size is 1</EM></CAPTION>

<TR><TH>Sections<TH>size_type alignment<TH>void * alignment<TH>requested_size alignment

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process

<TR><TD STYLE="background-color: gray; text-align: center;" ROWSPAN="4">Chunks section (16 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP to Chunk 2 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Chunk 1 (4 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">FLP to Chunk 3 (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Chunk 2 (4 bytes)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP to Chunk 4 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Chunk 3 (4 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">FLP to end-of-list (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Chunk 4 (4 bytes)

<TR><TD STYLE="background-color: silver; text-align: center;">Pointer to next Block (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Ptr to end-of-list (4 bytes)

<TR><TD STYLE="background-color: gray; text-align: center;">Size of next Block (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">0 (4 bytes)

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process
</TABLE>

<TABLE CELLSPACING="0" CELLPADDING="0" BORDER="3" STYLE="clear: both;" ALIGN=CENTER>
<CAPTION><EM>After user requests 7 contiguous elements of requested_size</EM></CAPTION>

<TR><TH>Sections<TH>size_type alignment<TH>void * alignment<TH>requested_size alignment

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process

<TR><TD STYLE="background-color: gray; text-align: center;" ROWSPAN="4">Chunks section (16 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">4 bytes in use by program
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">3 bytes in use by program (1 byte unused)
<TR><TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">FLP to Chunk 4 (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Chunk 3 (4 bytes)
<TR><TD STYLE="background-color: silver; text-align: center;">(4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">FLP to end-of-list (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">Chunk 4 (4 bytes)

<TR><TD STYLE="background-color: silver; text-align: center;">Pointer to next Block (4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">(4 bytes)
 <TD STYLE="background-color: gray; text-align: center;">Ptr to end-of-list (4 bytes)

<TR><TD STYLE="background-color: gray; text-align: center;">Size of next Block (4 bytes)
 <TD STYLE="background-color: silver; text-align: center;">0 (4 bytes)

<TR><TD STYLE="background-color: red; text-align: center;" COLSPAN="4">Memory not belonging to process
</TABLE>

<P>
Then, when the user deallocates the contiguous memory, we can split it up into chunks again.

<P>
Note that the implementation provided for allocating contiguous chunks uses a linear instead of quadratic algorithm.  This means that it <STRONG>may not find</STRONG> contiguous free chunks if the free list is not ordered.  Thus, it is recommended to always use an ordered free list when dealing with contiguous allocation of chunks.  (In the example above, if Chunk 1 pointed to Chunk 3 pointed to Chunk 2 pointed to Chunk 4, instead of being in order, the contiguous allocation algorithm would have failed to find any of the contiguous chunks).

<P>
<HR>

<P>
Copyright &copy; 2000, 2001 Stephen Cleary (<A HREF="mailto:shammah@voyager.net">shammah@voyager.net</A>)

<P>
This file can be redistributed and/or modified under the terms found in <A HREF="../copyright.html">copyright.html</A>

<P>
This software and its documentation is provided &quot;as is&quot; without express or implied warranty, and with no claim as to its suitability for any purpose.

</BODY>
</HTML>