| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 21 era <metadata dev> <origin dev> <block size>
24 metadata dev fast device holding the persistent metadata
45 Create a clone of the metadata, to allow a userland process to read it.
50 Drop the metadata snapshot.
55 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
56 <current era> <held metadata root | '-'>
59 metadata block size Fixed block size for each metadata block in
61 #used metadata blocks Number of metadata blocks used
62 #total metadata blocks Total number of metadata blocks
64 held metadata root The location, in blocks, of the metadata root
[all …]
|
| D | thin-provisioning.rst | 27 - Improve metadata resilience by storing metadata on a mirrored volume
30 - Improve performance by storing the metadata on SSD.
43 Userspace tools for checking and repairing the metadata have been fully
59 The pool device ties together the metadata volume and the data volume.
60 It maps I/O linearly to the data volume and updates the metadata via
71 Setting up a pool device requires a valid metadata device, and a
72 data device. If you do not have an existing metadata device you can
73 make one by zeroing the first 4k to indicate empty metadata.
77 The amount of metadata you need will vary according to how many blocks
79 less sharing than average you'll need a larger-than-average metadata device.
[all …]
|
| D | dm-zoned.rst | 27 internally for storing metadata and performaing reclaim operations.
40 metadata.
44 1) Metadata zones: these are conventional zones used to store metadata.
56 device being used. This allows reducing the amount of metadata needed to
59 The on-disk metadata format is as follows:
62 super block which describes the on disk amount and position of metadata
113 To protect metadata against corruption in case of sudden power loss or
114 system crash, 2 sets of metadata zones are used. One set, the primary
115 set, is used as the main metadata region, while the secondary set is
116 used as a staging area. Modified metadata is first written to the
[all …]
|
| D | cache.rst | 20 The target reuses the metadata library used in the thin-provisioning
56 3. A small metadata device - records which blocks are in the cache,
60 e.g. as a mirror for extra robustness. This metadata device may only
75 block sizes are bad because they increase the amount of metadata (both
86 the metadata.
131 Updating on-disk metadata
134 On-disk metadata is committed every time a FLUSH or FUA bio is written.
137 cache. If power is lost you may lose some recent writes. The metadata
181 cache <metadata dev> <cache dev> <origin dev> <block size>
186 metadata dev fast device holding the persistent metadata
[all …]
|
| D | dm-clone.rst | 29 The dm-clone target reuses the metadata library used by the thin-provisioning
58 3. A small metadata device - it records which regions are already valid in the
95 only updates its metadata.
124 Updating on-disk metadata
127 On-disk metadata is committed every time a FLUSH or FUA bio is written. If no
130 power is lost you may lose some recent writes. The metadata should always be
141 clone <metadata dev> <destination dev> <source dev> <region size>
145 metadata dev Fast device holding the persistent metadata
184 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
187 <clone metadata mode>
[all …]
|
| D | persistent-data.rst | 8 The more-sophisticated device-mapper targets require complex metadata
21 framework for people who want to store metadata in device-mapper
53 On power failure your metadata will be as it was when last committed.
59 dm-space-map-metadata.[hc]
66 the metadata space. The latter is complicated by the need to store
|
| D | dm-integrity.rst | 77 B - bitmap mode - data and metadata are written without any
79 regions where data and metadata don't match. This mode can
102 Don't interleave the data and metadata on on device. Use a
103 separate device for metadata.
168 less overhead there is for per-block integrity metadata.
177 The bitmap flush interval in milliseconds. The metadata buffers
192 storing LUKS metadata or for other purpose), the size of the reserved
203 metadata and padding). The user of this target should not send
218 * metadata area (4kiB), it contains journal entries
227 - every metadata sector ends with
[all …]
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.txt | 13 Almost all metadata on XFS is dynamically allocated. The only fixed location
14 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
15 other metadata structures need to be discovered by walking the filesystem
28 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata
39 One of the problems with the current metadata format is that apart from the
40 magic number in the metadata block, we have no other way of identifying what it
42 you can't look at a single metadata block in isolation and say "yes, it is
46 verification of metadata values, looking for values that are in range (and hence
53 Hence we need to record more information into the metadata to allow us to
54 quickly determine if the metadata is intact and can be ignored for the purpose
[all …]
|
| D | squashfs.txt | 114 Inodes are packed into the metadata blocks, and are not aligned to block
116 by a 48-bit number which encodes the location of the compressed metadata block
132 Like inodes, directories are packed into compressed metadata blocks, stored
140 compressed metadata block, and therefore, can share the start block.
150 in each metadata block. Directories are sorted in alphabetical order,
153 location of the metadata block the filename is in has been found.
154 The general idea of the index is to ensure only one metadata block needs to be
183 fragment lookup table is itself stored compressed into metadata blocks.
193 stored compressed into metadata blocks. A second index table is used to
207 This table is stored compressed into metadata blocks. A second index table is
[all …]
|
| /Linux-v5.4/samples/bpf/ |
| D | xdp_sample_pkts_kern.c | 27 } __packed metadata; in xdp_sample_prog() local
44 metadata.cookie = 0xdead; in xdp_sample_prog()
45 metadata.pkt_len = (u16)(data_end - data); in xdp_sample_prog()
46 sample_size = min(metadata.pkt_len, SAMPLE_SIZE); in xdp_sample_prog()
50 &metadata, sizeof(metadata)); in xdp_sample_prog()
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | dev-meta.rst | 20 intended for transfer of metadata between the userspace and the hardware and
23 The metadata interface is implemented on video device nodes. The device can be
24 dedicated to metadata or can support both video and metadata as specified in its
30 Device nodes supporting the metadata capture interface set the
33 ioctl. That flag means the device can capture metadata to memory. Similarly,
34 device nodes supporting metadata output interface set the
37 metadata from memory.
45 The metadata device uses the :ref:`format` ioctls to select the capture format.
46 The metadata buffer content format is bound to that selected format. In addition
69 :ref:`four character code <v4l2-fourcc>`. V4L2 defines metadata formats
|
| D | pixfmt-meta-d4xx.rst | 22 Intel D4xx (D435 and other) cameras include per-frame metadata in their UVC
24 means, that the private D4XX metadata, following the standard UVC header, is
26 proposed by Microsoft, and several proprietary ones. Supported standard metadata
29 document describes proprietary metadata types, used by D4xx cameras.
31 V4L2_META_FMT_D4XX buffers follow the metadata buffer layout of
36 Below are proprietary Microsoft style metadata types, used by D4xx cameras,
42 .. flat-table:: D4xx metadata
|
| /Linux-v5.4/samples/pidfd/ |
| D | Makefile | 3 hostprogs-y := pidfd-metadata
5 HOSTCFLAGS_pidfd-metadata.o += -I$(objtree)/usr/include
6 all: pidfd-metadata
|
| /Linux-v5.4/Documentation/block/ |
| D | data-integrity.rst | 8 Modern filesystems feature checksumming of data and metadata to
18 support for appending integrity metadata to an I/O. The integrity
19 metadata (or protection information in SCSI terminology) includes a
40 allow the operating system to interact with the integrity metadata
46 information to each sector. The data + integrity metadata is stored
53 encouraged them to allow separation of the data and integrity metadata
67 when writing and vice versa. This allows the integrity metadata to be
73 buffers and the integrity metadata. These two distinct buffers must
76 The separation of the data and integrity metadata buffers as well as
108 the kernel) is concerned, the integrity metadata is opaque information
[all …]
|
| /Linux-v5.4/drivers/md/ |
| D | dm-zoned-reclaim.c | 15 struct dmz_metadata *metadata; member
61 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_align_wp()
117 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_copy()
193 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_buf()
232 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_seq_data()
277 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_rnd_data()
327 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_empty()
343 struct dmz_metadata *zmd = zrc->metadata; in dmz_do_reclaim()
401 ret = dmz_flush_metadata(zrc->metadata); in dmz_do_reclaim()
427 struct dmz_metadata *zmd = zrc->metadata; in dmz_should_reclaim()
[all …]
|
| D | dm-zoned-target.c | 49 struct dmz_metadata *metadata; member
128 dmz_start_sect(dmz->metadata, zone) + dmz_blk2sect(chunk_block); in dmz_submit_bio()
181 dmz_id(dmz->metadata, zone), in dmz_handle_read()
190 ret = dmz_block_valid(dmz->metadata, zone, chunk_block); in dmz_handle_read()
205 ret = dmz_block_valid(dmz->metadata, bzone, chunk_block); in dmz_handle_read()
242 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_direct_write()
275 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_buffered_write()
318 dmz_id(dmz->metadata, zone), in dmz_handle_write()
343 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_discard()
380 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_bio()
[all …]
|
| /Linux-v5.4/tools/perf/util/ |
| D | cs-etm.c | 64 u64 **metadata; member
131 u64 *metadata; in cs_etm__get_magic() local
137 metadata = inode->priv; in cs_etm__get_magic()
138 *magic = metadata[CS_ETM_MAGIC]; in cs_etm__get_magic()
145 u64 *metadata; in cs_etm__get_cpu() local
151 metadata = inode->priv; in cs_etm__get_cpu()
152 *cpu = (int)metadata[CS_ETM_CPU]; in cs_etm__get_cpu()
383 u64 **metadata = etm->metadata; in cs_etm__set_trace_param_etmv3() local
386 t_params[idx].etmv3.reg_ctrl = metadata[idx][CS_ETM_ETMCR]; in cs_etm__set_trace_param_etmv3()
387 t_params[idx].etmv3.reg_trc_id = metadata[idx][CS_ETM_ETMTRACEIDR]; in cs_etm__set_trace_param_etmv3()
[all …]
|
| /Linux-v5.4/net/bridge/ |
| D | br_vlan_tunnel.c | 59 struct metadata_dst *metadata = NULL; in __vlan_tunnel_info_add() local
66 metadata = __ip_tun_set_dst(0, 0, 0, 0, 0, TUNNEL_KEY, in __vlan_tunnel_info_add()
68 if (!metadata) in __vlan_tunnel_info_add()
71 metadata->u.tun_info.mode |= IP_TUNNEL_INFO_TX | IP_TUNNEL_INFO_BRIDGE; in __vlan_tunnel_info_add()
72 vlan->tinfo.tunnel_dst = metadata; in __vlan_tunnel_info_add()
|
| /Linux-v5.4/drivers/soc/qcom/ |
| D | mdt_loader.c | 144 void *metadata; in __qcom_mdt_load() local
166 metadata = qcom_mdt_read_metadata(fw, &metadata_len); in __qcom_mdt_load()
167 if (IS_ERR(metadata)) { in __qcom_mdt_load()
168 ret = PTR_ERR(metadata); in __qcom_mdt_load()
172 ret = qcom_scm_pas_init_image(pas_id, metadata, metadata_len); in __qcom_mdt_load()
174 kfree(metadata); in __qcom_mdt_load()
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | verity.rst | 11 metadata is filesystem-specific. On ext4, the verity metadata is
37 They can have EXT4_ENCRYPT_FL set, in which case the verity metadata
41 metadata.
|
| /Linux-v5.4/include/uapi/linux/ |
| D | nvme_ioctl.h | 18 __u64 metadata; member
34 __u64 metadata; member
55 __u64 metadata; member
|
| /Linux-v5.4/net/sched/ |
| D | act_tunnel_key.c | 221 struct metadata_dst *metadata = NULL; in tunnel_key_init() local
305 metadata = __ip_tun_set_dst(saddr, daddr, tos, ttl, in tunnel_key_init()
316 metadata = __ipv6_tun_set_dst(&saddr, &daddr, tos, ttl, dst_port, in tunnel_key_init()
325 if (!metadata) { in tunnel_key_init()
332 ret = dst_cache_init(&metadata->u.tun_info.dst_cache, GFP_KERNEL); in tunnel_key_init()
339 &metadata->u.tun_info, in tunnel_key_init()
345 metadata->u.tun_info.mode |= IP_TUNNEL_INFO_TX; in tunnel_key_init()
384 params_new->tcft_enc_metadata = metadata; in tunnel_key_init()
405 if (metadata) in tunnel_key_init()
406 dst_release(&metadata->dst); in tunnel_key_init()
|
| /Linux-v5.4/fs/jffs2/ |
| D | fs.c | 61 mdatalen = f->metadata->size; in jffs2_do_setattr()
62 mdata = kmalloc(f->metadata->size, GFP_USER); in jffs2_do_setattr()
67 ret = jffs2_read_dnode(c, f, f->metadata, mdata, 0, mdatalen); in jffs2_do_setattr()
158 old_metadata = f->metadata; in jffs2_do_setattr()
167 f->metadata = NULL; in jffs2_do_setattr()
169 f->metadata = new_metadata; in jffs2_do_setattr()
326 if (f->metadata->size != sizeof(jdev.old_id) && in jffs2_iget()
327 f->metadata->size != sizeof(jdev.new_id)) { in jffs2_iget()
329 f->metadata->size); in jffs2_iget()
333 ret = jffs2_read_dnode(c, f, f->metadata, (char *)&jdev, 0, f->metadata->size); in jffs2_iget()
[all …]
|
| /Linux-v5.4/drivers/nvme/target/ |
| D | trace.h | 78 __field(u64, metadata)
91 __entry->metadata = le64_to_cpu(cmd->common.metadata);
100 __entry->flags, __entry->metadata,
|
| /Linux-v5.4/fs/xfs/ |
| D | Kconfig | 32 information as filesystem metadata and uses journaling to provide a
62 mechanism for ensuring data and metadata/log I/Os are completely
72 bool "XFS online metadata check support"
76 If you say Y here you will be able to check metadata on a
89 bool "XFS online metadata repair support"
93 If you say Y here you will be able to repair metadata on a
97 formatted with secondary metadata, such as reverse mappings and inode
|
