Lines Matching full:each

46 normal operation, each zone is assigned to a specific thread, and only that
48 Associated with each thread is a work queue. Each bio is associated with a
54 each zone has an implicit lock on the structures it manages for all its
58 Although each structure is divided into zones, this division is not
59 reflected in the on-disk representation of each data structure. Therefore,
60 the number of zones for each structure, and hence the number of threads,
61 can be reconfigured each time a vdo target is started.
83 Each block of data is hashed to produce a 16-byte block name. An index
90 storage, or reading and rehashing each block before overwriting it.
95 index as hints, and reads each indicated block to verify that it is indeed
127 mapping each block name to the chapter containing its newest record. This
150 entire block name (the key) for each entry, the entries are sorted by name
160 splitting its key space into many sub-lists, each starting at a fixed key
161 value, so that each individual list is short.
211 primary unit of application work in vdo. Each data_vio proceeds through a
233 block map (see below). In addition to the data blocks, each slab has a set
234 of reference counters, using 1 byte for each data block. Finally each slab
248 Each slab is independent of every other. They are assigned to "physical
254 online after a crash. The slab summary maintains an entry for each slab
257 how full it is. During recovery, each physical zone will attempt to recover
259 free blocks. Once each zone has some space, or has determined that none is
267 of as an array with one entry per logical address. Each entry is 5 bytes,
277 pages," each of which fits in a single 4K block. Each block map page
278 consists of a header and 812 mapping entries. Each mapping page is actually
279 a leaf of a radix tree which consists of block map pages at each level.
282 mod L.) At each level, the trees are interleaved, so logical addresses
293 the entire leaf level of the trees in memory, so each logical zone
302 slab depot. Each write request causes an entry to be made in the journal.
309 Each journal entry is an intent record summarizing the metadata updates
311 before each journal block write to ensure that the physical data for the
322 All write I/O to vdo is asynchronous. Each bio will be acknowledged as soon
404     The data_vio will search each slab in a zone until it finds a free
514     g. Each data_vio sets the compressed block as its new physical address.
526        possible. Each data_vio will then proceed to step 9 to record its
553     decrement entry for the old mapping. These two operations each require
560     order to avoid underflow. After each slab journal entry is made in
614 into the slab journals. Finally, each physical zone attempts to replay at
616 Once each zone has some free space (or has determined that it has none),
632 consistent with each other. This allows vdo to resume normal operation and