Lines Matching full:destination

11 existing, read-only source device into a writable destination device: It
18 and the copy of the source device to the destination device happens in the
27 replaced, e.g., by a linear table, mapping directly to the destination device.
36      The process of filling a region of the destination device with data from
38      source to the destination device.
40 Once a region gets hydrated we redirect all I/O regarding it to the destination
55 2. A destination device - the destination of the hydration, which will become a
59    destination device, i.e., which regions have already been hydrated, or have
62 The size of the destination device must be at least equal to the size of the
68 dm-clone divides the source and destination devices in fixed sized regions.
70 the source to the destination device.
77 Reads and writes from/to hydrated regions are serviced from the destination
87 destination device directly.
94 skips copying the region's data from the source to the destination device, and
97 If the destination device supports discards, then by default dm-clone will pass
103 dm-clone copies continuously from the source to the destination device, until
106 Copying data from the source to the destination device uses bandwidth. The user
115 destination device. By default, we issue copy requests of size equal to the
121 When the hydration of the destination device finishes, a dm event will be sent
141    clone <metadata dev> <destination dev> <source dev> <region size>
146  destination dev  The destination device, where the source will be cloned
164  no_discard_passdown  Disable passing down discards to the destination device
171                                   the source to the destination device at any
175                                   from the source to the destination device in
214       Disable the background hydration of the destination device.
217       Enable the background hydration of the destination device.
246 3. Enable background hydration of the destination device.
278    destination device, we print an error message, but the hydration process
326      destination of the cloning process and not restrict ourselves to
333    LV as dm-clone's destination device.