Searched full:origin (Results 1 – 25 of 47) sorted by relevance
12
| /Documentation/admin-guide/device-mapper/ |
| D | snapshot.rst | 12 - To merge a snapshot of a block device back into the snapshot's origin
20 the origin device.
24 snapshot, snapshot-origin, and snapshot-merge.
26 - snapshot-origin <origin>
34 - snapshot <origin> <COW device> <persistent?> <chunksize>
37 A snapshot of the <origin> block device is created. Changed chunks of
40 from <origin> for unchanged data. <COW device> will often be
41 smaller than the origin and if it fills up the snapshot will become
55 snapshot-origin or snapshot-merge target must be suspended. A failure to
56 suspend the origin target could result in data corruption.
[all …]
|
| D | cache.rst | 39 The origin device always contains a copy of the logical block, which
52 1. An origin device - the big, slow one.
66 The origin is divided up into blocks of a fixed size. This block size
89 complete until it has hit both the origin and cache devices. Clean
93 to be coherent with the origin device, then all reads are served from
94 the origin device (all reads miss the cache) and all writes are
95 forwarded to the origin device; additionally, write hits cause cache
121 Migrating data between the origin and cache device uses bandwidth.
170 state for all of the origin device (compare with the dirty bitset
181 cache <metadata dev> <cache dev> <origin dev> <block size>
[all …]
|
| D | thin-provisioning.rst | 186 N.B. If the origin device that you wish to snapshot is active, you
197 identifier for the origin device.
202 between the origin and the snapshot. Indeed the snapshot is no
216 You can use an external **read only** device as an origin for a
218 thin device will be passed through to the origin. Writes trigger
225 You must not write to the origin device if you use this technique!
232 You don't mention the origin at this stage.
240 Append an extra parameter to the thin target specifying the origin::
245 same extra origin parameter.
364 create_snap <dev id> <origin id>
[all …]
|
| D | era.rst | 21 era <metadata dev> <origin dev> <block size>
25 origin dev device holding data blocks that may change
26 block size block size of origin data device, granularity that is
|
| D | dm-init.rst | 55 `snapshot-origin` allowed
111 "snapshot-origin"::
113 dm-snap-orig,,4,ro,0 409600 snapshot-origin 8:2
|
| D | cache-policies.rst | 57 degrade slightly until smq recalculates the origin device's hotspots
117 cache <metadata dev> <cache dev> <origin dev> <block size>
|
| D | writecache.rst | 75 the origin volume in the last n milliseconds
|
| /Documentation/dev-tools/ |
| D | kmsan.rst | 95 incorrect shadow/origin values, likely leading to false positives. Functions
167 Origin tracking
170 Every four bytes of kernel memory also have a so-called origin mapped to them.
171 This origin describes the point in program execution at which the uninitialized
172 value was created. Every origin is associated with either the full allocation
176 When an uninitialized variable is allocated on stack or heap, a new origin
177 value is created, and that variable's origin is filled with that value. When a
178 value is read from memory, its origin is also read and kept together with the
179 shadow. For every instruction that takes one or more values, the origin of the
181 If a poisoned value is written into memory, its origin is written to the
[all …]
|
| D | kcsan.rst | 61 race at unknown origin, with read to 0xffffffffc009bdb0 of 8 bytes by task 515 on cpu 2:
272 after delay; if the values mismatch, we infer a race of unknown origin.
|
| /Documentation/maintainer/ |
| D | modifying-patches.rst | 9 rule (c) of the developers certificate of origin, you should ask the submitter
30 to insert an indication of the origin of a patch at the top of the commit
|
| D | pull-requests.rst | 30 practice is to include in the name an indicator of the subsystem of origin
127 git push origin char-misc-4.15-rc1
|
| D | messy-diffstat.rst | 64 and the second origin end point (vN-rc2), which is certainly not what our
|
| /Documentation/virt/kvm/s390/ |
| D | s390-pv-boot.rst | 49 * PV Header origin
53 * Origin
|
| /Documentation/filesystems/ |
| D | overlayfs.rst | 512 filesystem, are encoded and stored in the "trusted.overlay.origin" extended
515 to the stored origin in upper root directory. On failure to verify the
516 lower root origin, mount will fail with ESTALE. An overlayfs mount with
634 attribute "trusted.overlay.origin" on the upper inode.
640 match the origin file handle that was stored at copy_up time. If a
641 found lower directory does not match the stored origin, that directory
654 hexadecimal representation of the copy up origin file handle. For a
664 2. For an indexed object, encode a lower file handle from copy_up origin
675 are stored in extended attribute "trusted.overlay.origin".
696 "redirect" origin directory, cannot be used to find the middle or upper
[all …]
|
| /Documentation/admin-guide/ |
| D | quickly-build-trimmed-linux.rst | 43 git fetch --depth 1 origin
45 git checkout --force --detach origin/master
146 git fetch --shallow-exclude=v6.0 origin
152 git remote set-branches --add origin linux-6.1.y
153 git fetch --shallow-exclude=v6.0 origin
159 git checkout --detach origin/master
161 If you deepened your clone, you instead of ``origin/master`` can specify the
293 git remote set-branches --add origin linux-6.2.y
299 git fetch --shallow-exclude=v6.0 origin
305 git checkout --force --detach origin/master
[all …]
|
| D | bug-bisect.rst | 132 your work - the Developer's Certificate of Origin'.
|
| /Documentation/sphinx/ |
| D | load_config.py | 16 configuration values from the origin ``conf.py``. With this you are able to
|
| /Documentation/translations/zh_CN/maintainer/ |
| D | pull-requests.rst | 111 git push origin char-misc-4.15-rc1
|
| /Documentation/input/devices/ |
| D | atarikbd.rst | 93 Note that the sign of the delta y reported is a function of the Y origin
202 either axis and the Y=0 origin at the top of the screen, and joystick event
305 command is not affected by the mouse motion origin.
381 This command makes the origin of the Y axis to be at the bottom of the
393 Makes the origin of the Y axis to be at the top of the logical coordinate
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-cropcap.rst | 67 choose origin and units of the coordinate system in the analog
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-links.rst | 121 - Pad at the origin of this link.
|
| /Documentation/ABI/testing/ |
| D | dev-kmsg | 21 facility number LOG_KERN (0), to make sure that the origin of
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 63 about Linux's nice level support was its asymmetry around the origin
|
| /Documentation/driver-api/media/drivers/ |
| D | sh_mobile_ceu_camera.rst | 121 "...specification does not define an origin or units. However by convention
|
| /Documentation/devicetree/bindings/media/ |
| D | video-interface-devices.yaml | 35 pixel array read-out order. The origin is set to the first pixel being
53 reference system on the focal plane of the camera module. The origin is
|
12