Lines Matching full:regions

58 3. A small metadata device - it records which regions are already valid in the
59    destination device, i.e., which regions have already been hydrated, or have
65 Regions  section in Design
68 dm-clone divides the source and destination devices in fixed sized regions.
69 Regions are the unit of hydration, i.e., the minimum amount of data copied from
77 Reads and writes from/to hydrated regions are serviced from the destination
93 as a hint to skip hydration of the regions covered by the request, i.e., it
111 A message `hydration_threshold <#regions>` can be used to set the maximum number
112 of regions being copied, the default being 1 region.
116 region size. A message `hydration_batch_size <#regions>` can be used to tune the
118 dm-clone trying to batch together contiguous regions, so we copy the data in
119 batches of this many regions.
170  hydration_threshold <#regions>   Maximum number of regions being copied from
173  hydration_batch_size <#regions>  During background hydration, try to batch
174                                   together contiguous regions, so we copy data
176                                   batches of this many regions.
185    <region size> <#hydrated regions>/<#total regions> <#hydrating regions>
194  #hydrated regions       Number of regions that have finished hydrating
195  #total regions          Total number of regions to hydrate
196  #hydrating regions      Number of regions currently hydrating
219   `hydration_threshold <#regions>`
222   `hydration_batch_size <#regions>`
267 1. We redirect reads, to not-yet-hydrated regions, to the source device. If
269    the same regions, this behaviour could degrade performance. We should use
270    these reads as hints to hydrate the relevant regions sooner. Currently, we
271    rely on the page cache to cache these regions, so we hopefully don't end up
274 2. Release in-core resources, i.e., the bitmaps tracking which regions are