Searched refs:deduplication (Results 1 – 14 of 14) sorted by relevance
| /linux/Documentation/arch/powerpc/ |
| H A D | vmemmap_dedup.rst | 7 The device-dax interface uses the tail deduplication technique explained in 10 On powerpc, vmemmap deduplication is only used with radix MMU translation. Also 12 deduplication. 16 vmemmap deduplication possible.
|
| /linux/drivers/md/dm-vdo/ |
| H A D | Kconfig | 4 tristate "VDO: deduplication and compression target" 13 deduplication, compression and thin-provisioning.
|
| H A D | types.h | 226 bool deduplication; member
|
| H A D | dm-vdo-target.c | 598 return parse_bool(value, "on", "off", &config->deduplication); in parse_one_key_value_pair() 759 config->deduplication = true; in parse_device_config() 1464 vdo_log_debug("Deduplication = %s", (config->deduplication ? "on" : "off")); in vdo_initialize() 2244 if (vdo->device_config->deduplication) { in load_callback()
|
| H A D | dedupe.c | 2590 if (config->deduplication) { in resume_index()
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | vdo-design.rst | 7 The dm-vdo (virtual data optimizer) target provides inline deduplication, 16 Because deduplication rates fall drastically as the block size increases, a 18 deduplication rates of 254:1, i.e. up to 254 copies of a given 4K block can 25 The design of dm-vdo is based on the idea that deduplication is a two-part 28 parts: a deduplication index (called UDS) that is used to discover 39 block sizes in order to achieve good deduplication rates, acceptable 78 ultimate goal of deduplication is to reduce storage costs. Since there is a 166 called the deduplication window. If new writes duplicate data that is older 171 result in no deduplication, because the beginning of the file will no 176 deduplication beyond the 256GB threshold, vdo can be configured to use a [all …]
|
| H A D | vdo.rst | 8 block-level deduplication, compression, and thin provisioning. As a device 43 deduplication and compression is not cancelled out by the metadata 137 deduplication based on the hash value of data blocks. The 166 deduplication: 167 Whether deduplication is enabled. The default is 'on'; the 180 <maxDiscard>, <compression>, and <deduplication>. 302 The current state of the deduplication index in the vdo 330 The deduplication index requires additional memory which scales with the 331 size of the deduplication window. For dense indexes, the index requires 1
|
| /linux/Documentation/mm/ |
| H A D | ksm.rst | 45 The deduplication limit enforced by ``max_page_sharing`` is required 60 deduplication factor at the expense of slower worst case for rmap
|
| H A D | vmemmap_dedup.rst | 188 The device-dax interface uses the same tail deduplication technique explained 202 System RAM ranges initialized at boot. Thus the tail page deduplication
|
| /linux/Documentation/filesystems/ |
| H A D | btrfs.rst | 23 * Reflink, deduplication
|
| H A D | erofs.rst | 70 - Support chunk-based data deduplication and rolling-hash compressed data 71 deduplication; 277 In order to support chunk-based data deduplication, a new inode data layout has 377 therefore it can be used for compressed data deduplication.
|
| /linux/fs/erofs/ |
| H A D | Kconfig | 30 chunk-based deduplication ensure space efficiency while maintaining 37 compression and fine-grained deduplication. It utilizes fixed-size
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | ksm.rst | 137 deduplication limit to avoid high latency for virtual memory 142 deduplication factor will be, but the slower the worst case 155 that hit the deduplication limit for stale information.
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-online-fsck-design.rst | 971 defeats device-level deduplication because the filesystem requires real
|