| /design/trunk/src/ch_ds.xml |
|---|
| 36,7 → 36,7 |
| space and are more general. On the other hand, they are slower than |
| in-array FIFOs and can be hardly used to implement buffers.</para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="list" xreflabel=""> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/list.pdf" format="PDF" /> |
| 76,7 → 76,7 |
| inactive ASIDs or in userspace keyboard driver to buffer read |
| characters.</para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="fifo" xreflabel=""> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/fifo.pdf" format="PDF" /> |
| 110,7 → 110,7 |
| a dynamically allocated array of list heads that represent each chain, |
| number of chains and the maximal number of keys.</para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="hash" xreflabel=""> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/hash.pdf" format="PDF" /> |
| 159,7 → 159,7 |
| data. Moreover, B+trees can be used for easy storing, resizing and merging |
| of disjunctive intervals.</para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="btree" xreflabel=""> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/btree.pdf" format="PDF" /> |
| /design/trunk/src/ch_arch_overview.xml |
|---|
| 19,7 → 19,7 |
| be used even without some traditional subsystems (e.g. block devices, |
| filesystems and networking).</para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="arch1"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/arch1.pdf" format="PDF"/> |
| /design/trunk/src/ch_memory_management.xml |
|---|
| 57,7 → 57,7 |
| allocation requests, the frame allocator is tightly integrated with the |
| buddy system belonging to the zone. The frame allocator is also |
| responsible for updating information about the number of free and busy |
| frames in the zone. <figure> |
| frames in the zone. <figure float="1"> |
| <mediaobject id="frame_alloc"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/frame_alloc.pdf" format="PDF" /> |
| 122,7 → 122,7 |
| size. On the other hand, the buddy allocator suffers increased internal |
| fragmentation of memory and is not suitable for general kernel |
| allocations. This purpose is better addressed by the <link |
| linkend="slab">slab allocator</link>.<figure> |
| linkend="slab">slab allocator</link>.<figure float="1"> |
| <mediaobject id="buddy_alloc"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/buddy_alloc.pdf" format="PDF" /> |
| 245,7 → 245,7 |
| it is immediately freed.</para> |
| <para> |
| <figure> |
| <figure float="1"> |
| <mediaobject id="slab_alloc"> |
| <imageobject role="pdf"> |
| <imagedata fileref="images.vector/slab_alloc.pdf" format="PDF" /> |
| /design/trunk/src/ch_scheduling.xml |
|---|
| 141,7 → 141,7 |
| <constant>Undead</constant> state. When the thread is detached or |
| detaches itself during its life, it is destroyed in the |
| <constant>Exiting</constant> state and the <constant>Undead</constant> |
| state is not reached.<figure> |
| state is not reached.<figure float="1"> |
| <title>Transitions among thread states.</title> |
| <mediaobject id="thread_states" xreflabel=""> |