| /Linux-v5.10/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 4 XFS Self Describing Metadata
16 Almost all metadata on XFS is dynamically allocated. The only fixed location
17 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
18 other metadata structures need to be discovered by walking the filesystem
31 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata
39 Self Describing Metadata
42 One of the problems with the current metadata format is that apart from the
43 magic number in the metadata block, we have no other way of identifying what it
45 you can't look at a single metadata block in isolation and say "yes, it is
49 verification of metadata values, looking for values that are in range (and hence
[all …]
|
| D | squashfs.rst | 36 Metadata compression yes no
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
120 Inodes are packed into the metadata blocks, and are not aligned to block
122 by a 48-bit number which encodes the location of the compressed metadata block
138 Like inodes, directories are packed into compressed metadata blocks, stored
146 compressed metadata block, and therefore, can share the start block.
156 in each metadata block. Directories are sorted in alphabetical order,
159 location of the metadata block the filename is in has been found.
160 The general idea of the index is to ensure only one metadata block needs to be
189 fragment lookup table is itself stored compressed into metadata blocks.
[all …]
|
| /Linux-v5.10/drivers/md/ |
| D | dm-clone-metadata.h | 10 #include "persistent-data/dm-space-map-metadata.h"
15 * The metadata device is currently limited in size.
20 * A metadata device larger than 16GB triggers a warning.
26 /* dm-clone metadata */
32 * @cmd: The dm-clone metadata
43 * @cmd: The dm-clone metadata
55 * Read existing or create fresh metadata.
57 * @bdev: The device storing the metadata
61 * @returns: The dm-clone metadata
64 * If it is, it formats @bdev and creates fresh metadata. If it isn't, it
[all …]
|
| D | dm-zoned-target.c | 49 /* For metadata handling */
50 struct dmz_metadata *metadata; member
135 dmz_start_sect(dmz->metadata, zone) + dmz_blk2sect(chunk_block); in dmz_submit_bio()
173 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_read()
255 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_direct_write()
288 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_buffered_write()
322 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_write()
361 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_discard()
375 dmz_metadata_label(dmz->metadata), in dmz_handle_discard()
401 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_bio()
[all …]
|
| D | dm-thin-metadata.h | 12 #include "persistent-data/dm-space-map-metadata.h"
17 * The metadata device is currently limited in size.
22 * A metadata device larger than 16GB triggers a warning.
29 * Thin metadata superblock flags.
42 * Reopens or creates a new, empty metadata volume.
52 * specified below will prevent use of the thin metadata.
73 * Deletes a virtual device from the metadata. It _is_ safe to call this
81 * Commits _all_ metadata changes: device creation, deletion, mapping
109 * The metadata snapshot is a copy of the current superblock (minus the
112 * copy of the metadata to userland due to extra copy-on-write operations
[all …]
|
| /Linux-v5.10/Documentation/admin-guide/device-mapper/ |
| D | thin-provisioning.rst | 24 Metadata is stored on a separate device from data, giving the
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
[all …]
|
| 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 | dm-zoned.rst | 27 internally for storing metadata and performaing reclaim operations.
40 metadata. It can also use a regular block device together with the zoned
48 1) Metadata zones: these are conventional zones used to store metadata.
49 Metadata zones are not reported as useable capacity to the user.
60 device being used. This allows reducing the amount of metadata needed to
63 The on-disk metadata format is as follows:
66 super block which describes the on disk amount and position of metadata
114 Metadata Protection
117 To protect metadata against corruption in case of sudden power loss or
118 system crash, 2 sets of metadata zones are used. One set, the primary
[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 | 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 the 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
208 storing LUKS metadata or for other purpose), the size of the reserved
219 metadata and padding). The user of this target should not send
234 * metadata area (4kiB), it contains journal entries
243 - every metadata sector ends with
[all …]
|
| /Linux-v5.10/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_surface.c | 45 * @srf: The surface metadata.
202 return srf->metadata.num_sizes * sizeof(struct vmw_surface_dma); in vmw_surface_dma_size()
216 return sizeof(struct vmw_surface_define) + srf->metadata.num_sizes * in vmw_surface_define_size()
265 cmd_len = sizeof(cmd->body) + srf->metadata.num_sizes * in vmw_surface_define_encode()
276 cmd->body.surfaceFlags = (SVGA3dSurface1Flags)srf->metadata.flags; in vmw_surface_define_encode()
277 cmd->body.format = srf->metadata.format; in vmw_surface_define_encode()
279 cmd->body.face[i].numMipLevels = srf->metadata.mip_levels[i]; in vmw_surface_define_encode()
283 src_size = srf->metadata.sizes; in vmw_surface_define_encode()
285 for (i = 0; i < srf->metadata.num_sizes; ++i, cmd_size++, src_size++) { in vmw_surface_define_encode()
309 svga3dsurface_get_desc(srf->metadata.format); in vmw_surface_dma_encode()
[all …]
|
| /Linux-v5.10/drivers/staging/media/atomisp/pci/runtime/isys/src/ |
| D | virtual_isys.c | 37 bool metadata,
55 bool metadata);
119 bool metadata,
124 bool metadata,
141 bool metadata,
176 isys_stream->enable_metadata = isys_stream_descr->metadata.enable; in ia_css_isys_stream_create()
203 /* create metadata channel */ in ia_css_isys_stream_create()
204 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_create()
225 /* Destroy metadata channel only if its allocated*/ in ia_css_isys_stream_destroy()
254 /* configure metadata channel */ in ia_css_isys_stream_calculate_cfg()
[all …]
|
| /Linux-v5.10/drivers/staging/media/atomisp/pci/ |
| D | ia_css_metadata.h | 20 * This file contains structure for processing sensor metadata.
27 /* Metadata configuration. This data structure contains necessary info
28 * to process sensor metadata.
53 /* @brief Allocate a metadata buffer.
54 * @param[in] metadata_info Metadata info struct, contains details on metadata buffers.
55 * @return Pointer of metadata buffer or NULL (if error)
57 * This function allocates a metadata buffer according to the properties
63 /* @brief Free a metadata buffer.
65 * @param[in] metadata Pointer of metadata buffer.
68 * This function frees a metadata buffer.
[all …]
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | dev-meta.rst | 6 Metadata Interface
9 Metadata refers to any non-image data that supplements video frames with
13 intended for transfer of metadata between the userspace and the hardware and
16 The metadata interface is implemented on video device nodes. The device can be
17 dedicated to metadata or can support both video and metadata as specified in its
23 Device nodes supporting the metadata capture interface set the
26 ioctl. That flag means the device can capture metadata to memory. Similarly,
27 device nodes supporting metadata output interface set the
30 metadata from memory.
38 The metadata device uses the :ref:`format` ioctls to select the capture format.
[all …]
|
| /Linux-v5.10/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.10/samples/bpf/ |
| D | xdp_sample_pkts_kern.c | 21 /* Metadata will be in the perf event before the packet data. */ in xdp_sample_prog()
25 } __packed metadata; in xdp_sample_prog() local
42 metadata.cookie = 0xdead; in xdp_sample_prog()
43 metadata.pkt_len = (u16)(data_end - data); in xdp_sample_prog()
44 sample_size = min(metadata.pkt_len, SAMPLE_SIZE); in xdp_sample_prog()
48 &metadata, sizeof(metadata)); in xdp_sample_prog()
|
| /Linux-v5.10/Documentation/driver-api/dmaengine/ |
| D | client.rst | 156 **Optional: per descriptor metadata**
158 DMAengine provides two ways for metadata support.
162 The metadata buffer is allocated/provided by the client driver and it is
172 The metadata buffer is allocated/managed by the DMA driver. The client
174 the metadata and can directly update or read it.
176 Becasue the DMA driver manages the memory area containing the metadata,
180 metadata must not be accessed after issue_pending.
181 In other words: if the aim is to read back metadata after the transfer is
206 construct the metadata in the client's buffer
217 4. when the transfer is completed, the metadata should be available in the
[all …]
|
| /Linux-v5.10/fs/nilfs2/ |
| D | alloc.c | 23 * @inode: inode of metadata file using this allocator
34 * @inode: inode of metadata file using this allocator
44 * @inode: inode of metadata file using this allocator
78 * @inode: inode of metadata file using this allocator
93 * @inode: inode of metadata file using this allocator
109 * @inode: inode of metadata file using this allocator
162 * @inode: inode of metadata file using this allocator
178 * @inode: inode of metadata file
234 * @inode: inode of metadata file using this allocator
254 * @inode: inode of metadata file using this allocator
[all …]
|
| /Linux-v5.10/fs/xfs/ |
| D | Kconfig | 31 by the V5 format, such as metadata checksumming, strengthened
32 metadata verification, and the ability to store timestamps past the
57 information as filesystem metadata and uses journaling to provide a
87 mechanism for ensuring data and metadata/log I/Os are completely
97 bool "XFS online metadata check support"
101 If you say Y here you will be able to check metadata on a
114 bool "XFS online metadata repair support"
118 If you say Y here you will be able to repair metadata on a
122 formatted with secondary metadata, such as reverse mappings and inode
|
| D | xfs_health.c | 19 * Warn about metadata corruption that we detected but haven't fixed, and
66 "Uncorrected metadata errors detected; please run xfs_repair."); in xfs_health_unmount()
69 * We discovered uncorrected metadata problems at some point in xfs_health_unmount()
92 /* Mark unhealthy per-fs metadata. */
107 /* Mark a per-fs metadata healed. */
122 /* Sample which per-fs metadata are unhealthy. */
135 /* Mark unhealthy realtime metadata. */
150 /* Mark a realtime metadata healed. */
165 /* Sample which realtime metadata are unhealthy. */
178 /* Mark unhealthy per-ag metadata. */
[all …]
|
| /Linux-v5.10/fs/xfs/scrub/ |
| D | scrub.c | 33 * scrub & repair, on the other hand, enables us to check the metadata
37 * Given that most XFS metadata consist of records stored in a btree,
42 * misunderstandings between pieces of metadata.
44 * It is expected that the checkers responsible for per-AG metadata
46 * metadata structure, and perform any relevant cross-referencing before
67 * if there is a cycle in the metadata. The basic problem is that
86 * the metadata is correct but otherwise suboptimal, the PREEN flag
89 * We perform secondary validation of filesystem metadata by
90 * cross-referencing every record with all other available metadata.
94 * mapping btree. Inconsistent metadata is noted by setting the
[all …]
|
| D | scrub.h | 14 ST_PERAG, /* per-AG metadata */
15 ST_FS, /* per-FS metadata */
16 ST_INODE, /* per-inode metadata */
24 /* Examine metadata for errors. */
27 /* Repair or optimize the metadata. */
30 /* Decide if we even have this piece of metadata. */
70 * The XFS_SICK_* flags that correspond to the metadata being scrubbed
86 /* Metadata scrubbers */
|
| /Linux-v5.10/fs/xfs/libxfs/ |
| D | xfs_health.h | 16 * shutdowns due to corrupt metadata.
18 * The online scrub feature evaluates the health of all filesystem metadata.
19 * When scrub detects corruption in a piece of metadata it will set the
25 * "checked" field tell us if a given piece of metadata has ever been examined,
29 * - checked && sick => metadata needs repair
30 * - checked && !sick => metadata is ok
39 /* Observable health issues for metadata spanning the entire filesystem. */
45 /* Observable health issues for realtime volume metadata. */
49 /* Observable health issues for AG metadata. */
61 /* Observable health issues for inode metadata. */
|
| /Linux-v5.10/drivers/thunderbolt/ |
| D | usb4.c | 95 static int usb4_switch_op_read_metadata(struct tb_switch *sw, u32 *metadata) in usb4_switch_op_read_metadata() argument
97 return tb_sw_read(sw, metadata, TB_CFG_SWITCH, ROUTER_CS_25, 1); in usb4_switch_op_read_metadata()
100 static int usb4_switch_op_write_metadata(struct tb_switch *sw, u32 metadata) in usb4_switch_op_write_metadata() argument
102 return tb_sw_write(sw, &metadata, TB_CFG_SWITCH, ROUTER_CS_25, 1); in usb4_switch_op_write_metadata()
344 u32 metadata; in usb4_switch_drom_read_block() local
347 metadata = (dwords << USB4_DROM_SIZE_SHIFT) & USB4_DROM_SIZE_MASK; in usb4_switch_drom_read_block()
348 metadata |= (dwaddress << USB4_DROM_ADDRESS_SHIFT) & in usb4_switch_drom_read_block()
351 ret = usb4_switch_op_write_metadata(sw, metadata); in usb4_switch_drom_read_block()
511 u32 metadata; in usb4_switch_nvm_sector_size() local
522 ret = usb4_switch_op_read_metadata(sw, &metadata); in usb4_switch_nvm_sector_size()
[all …]
|
