| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | xdp-rx-metadata.rst | 2 XDP RX Metadata
6 hardware metadata related to a packet using a set of helper functions,
7 and how it can pass that metadata on to other consumers.
12 XDP has access to a set of kfuncs to manipulate the metadata in an XDP frame.
13 Every device driver that wishes to expose additional packet metadata can
18 metadata is supported, this set will grow:
23 An XDP program can use these kfuncs to read the metadata into stack
24 variables for its own consumption. Or, to pass the metadata on to other
25 consumers, an XDP program can store it into the metadata area carried
27 metadata available in which case the driver returns ``-ENODATA``.
[all …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 5 XFS Self Describing Metadata
17 Almost all metadata on XFS is dynamically allocated. The only fixed location
18 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
19 other metadata structures need to be discovered by walking the filesystem
32 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata
40 Self Describing Metadata
43 One of the problems with the current metadata format is that apart from the
44 magic number in the metadata block, we have no other way of identifying what it
46 you can't look at a single metadata block in isolation and say "yes, it is
50 verification of metadata values, looking for values that are in range (and hence
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_surface.c | 48 * @srf: The surface metadata.
199 return srf->metadata.num_sizes * sizeof(struct vmw_surface_dma); in vmw_surface_dma_size()
213 return sizeof(struct vmw_surface_define) + srf->metadata.num_sizes * in vmw_surface_define_size()
262 cmd_len = sizeof(cmd->body) + srf->metadata.num_sizes * in vmw_surface_define_encode()
273 cmd->body.surfaceFlags = (SVGA3dSurface1Flags)srf->metadata.flags; in vmw_surface_define_encode()
274 cmd->body.format = srf->metadata.format; in vmw_surface_define_encode()
276 cmd->body.face[i].numMipLevels = srf->metadata.mip_levels[i]; in vmw_surface_define_encode()
280 src_size = srf->metadata.sizes; in vmw_surface_define_encode()
282 for (i = 0; i < srf->metadata.num_sizes; ++i, cmd_size++, src_size++) { in vmw_surface_define_encode()
306 vmw_surface_get_desc(srf->metadata.format); in vmw_surface_dma_encode()
[all …]
|
| /kernel/linux/linux-6.6/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()
192 /* create metadata channel */ in ia_css_isys_stream_create()
193 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_create()
214 /* Destroy metadata channel only if its allocated*/ in ia_css_isys_stream_destroy()
243 /* configure metadata channel */ in ia_css_isys_stream_calculate_cfg()
[all …]
|
| /kernel/linux/linux-6.6/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 performing 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 usable 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-integrity.rst | 41 Accesses to the on-disk metadata area containing checksums (aka tags) are
42 buffered using dm-bufio. When an access to any given metadata area
43 occurs, each unique metadata area gets its own buffer(s). The buffer size
44 is capped at the size of the metadata area, but may be smaller, thereby
45 requiring multiple buffers to represent the full metadata area. A smaller
47 metadata area for small reads/writes. The metadata is still read even in
86 B - bitmap mode - data and metadata are written without any
88 regions where data and metadata don't match. This mode can
111 Don't interleave the data and metadata on the device. Use a
112 separate device for 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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.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 …]
|