| /linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 4 XDP RX Metadata
8 hardware metadata related to a packet using a set of helper functions,
9 and how it can pass that metadata on to other consumers.
14 XDP has access to a set of kfuncs to manipulate the metadata in an XDP frame.
15 Every device driver that wishes to expose additional packet metadata can
20 metadata is supported, this set will grow:
31 An XDP program can use these kfuncs to read the metadata into stack
32 variables for its own consumption. Or, to pass the metadata on to other
33 consumers, an XDP program can store it into the metadata area carried
35 metadata available in which case the driver returns ``-ENODATA``.
[all …]
|
| H A D | xsk-tx-metadata.rst | 4 AF_XDP TX Metadata
8 via :doc:`af_xdp`. Refer to :doc:`xdp-rx-metadata` on how to access similar
9 metadata on the receive side.
14 The headroom for the metadata is reserved via ``tx_metadata_len`` and
15 ``XDP_UMEM_TX_METADATA_LEN`` flag in ``struct xdp_umem_reg``. The metadata
17 The metadata layout is a fixed UAPI, refer to ``union xsk_tx_metadata`` in
25 The headroom and the metadata itself should be located right before
26 ``xdp_desc->addr`` in the umem frame. Within a frame, the metadata
42 any metadata (i.e., the ones that don't have ``XDP_TX_METADATA`` option),
43 the metadata area is ignored by the kernel as well.
[all …]
|
| /linux/Documentation/filesystems/xfs/ |
| H A 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 …]
|
| /linux/drivers/md/ |
| H A 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 …]
|
| H A D | dm-zoned-target.c | 49 /* For metadata handling */
50 struct dmz_metadata *metadata; member
134 dmz_start_sect(dmz->metadata, zone) + dmz_blk2sect(chunk_block); in dmz_submit_bio()
172 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_read()
254 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_direct_write()
287 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_buffered_write()
321 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_write()
360 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_discard()
374 dmz_metadata_label(dmz->metadata), in dmz_handle_discard()
400 struct dmz_metadata *zmd = dmz->metadata; in dmz_handle_bio()
[all …]
|
| H A D | dm-thin-metadata.h | 13 #include "persistent-data/dm-space-map-metadata.h"
18 * The metadata device is currently limited in size.
23 * A metadata device larger than 16GB triggers a warning.
30 * Thin metadata superblock flags.
43 * Reopens or creates a new, empty metadata volume.
53 * specified below will prevent use of the thin metadata.
74 * Deletes a virtual device from the metadata. It _is_ safe to call this
82 * Commits _all_ metadata changes: device creation, deletion, mapping
110 * The metadata snapshot is a copy of the current superblock (minus the
113 * copy of the metadata to userland due to extra copy-on-write operations
[all …]
|
| H A D | dm-clone-metadata.c | 19 #include "dm-clone-metadata.h"
21 #define DM_MSG_PREFIX "clone metadata"
31 /* Min and max dm-clone metadata versions supported */
36 * On-disk metadata layout
70 * In order to track which regions are hydrated during a metadata transaction,
73 * tracks the regions that got hydrated during the current metadata
78 * current metadata transaction and update the metadata accordingly, when we
80 * only commit the metadata of regions that were properly flushed to the
89 * During a metadata commit we scan dmap->dirty_words and dmap->dirty_regions
90 * and update the on-disk metadata accordingly. Thus, we don't have to flush to
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| H A 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
116 Don't interleave the data and metadata on the device. Use a
117 separate device for metadata.
[all …]
|
| H A 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 …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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 …]
|
| H A D | metafmt-d4xx.rst | 9 Intel D4xx UVC Cameras Metadata
15 Intel D4xx (D435, D455 and others) cameras include per-frame metadata in their UVC
17 means, that the private D4XX metadata, following the standard UVC header, is
19 proposed by Microsoft, and several proprietary ones. Supported standard metadata
22 document describes proprietary metadata types, used by D4xx cameras.
24 V4L2_META_FMT_D4XX buffers follow the metadata buffer layout of
31 Below are proprietary Microsoft style metadata types, used by D4xx cameras,
37 .. flat-table:: D4xx metadata
251 [9] LibRealSense SDK metadata source:
252 https://github.com/IntelRealSense/librealsense/blob/master/src/metadata.h
|
| /linux/tools/perf/util/ |
| H A D | bpf-event.c | 345 struct bpf_metadata *metadata; in bpf_metadata_alloc() local
348 metadata = zalloc(sizeof(struct bpf_metadata)); in bpf_metadata_alloc()
349 if (!metadata) in bpf_metadata_alloc()
352 metadata->prog_names = zalloc(nr_prog_tags * sizeof(char *)); in bpf_metadata_alloc()
353 if (!metadata->prog_names) { in bpf_metadata_alloc()
354 bpf_metadata_free(metadata); in bpf_metadata_alloc()
358 metadata->prog_names[prog_index] = zalloc(BPF_PROG_NAME_LEN); in bpf_metadata_alloc()
359 if (!metadata->prog_names[prog_index]) { in bpf_metadata_alloc()
360 bpf_metadata_free(metadata); in bpf_metadata_alloc()
363 metadata->nr_prog_names++; in bpf_metadata_alloc()
[all …]
|
| H A D | cs-etm.c | 79 u64 **metadata; member
119 /* Conversion between traceID and metadata pointers */
166 u64 *metadata; in cs_etm__get_magic() local
172 metadata = inode->priv; in cs_etm__get_magic()
173 *magic = metadata[CS_ETM_MAGIC]; in cs_etm__get_magic()
180 u64 *metadata; in cs_etm__get_cpu() local
186 metadata = inode->priv; in cs_etm__get_cpu()
187 *cpu = (int)metadata[CS_ETM_CPU]; in cs_etm__get_cpu()
207 static enum cs_etm_pid_fmt cs_etm__init_pid_fmt(u64 *metadata) in cs_etm__init_pid_fmt() argument
211 if (metadata[CS_ETM_MAGI in cs_etm__init_pid_fmt()
786 cs_etm__set_trace_param_etmv3(struct cs_etm_trace_params * t_params,u64 * metadata,u32 etmidr) cs_etm__set_trace_param_etmv3() argument
794 cs_etm__set_trace_param_etmv4(struct cs_etm_trace_params * t_params,u64 * metadata) cs_etm__set_trace_param_etmv4() argument
806 cs_etm__set_trace_param_ete(struct cs_etm_trace_params * t_params,u64 * metadata) cs_etm__set_trace_param_ete() argument
824 u64 *metadata = inode->priv; cs_etm__init_trace_params() local
2950 u64 *metadata = NULL; cs_etm__create_meta_blk() local
3211 cs_etm__has_virtual_ts(u64 ** metadata,int num_cpu) cs_etm__has_virtual_ts() argument
3235 cs_etm__map_trace_ids_metadata(struct cs_etm_auxtrace * etm,int num_cpu,u64 ** metadata) cs_etm__map_trace_ids_metadata() argument
3362 u64 **metadata = NULL; cs_etm__process_auxtrace_info_full() local
[all...] |
| /linux/Documentation/block/ |
| H A 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/drivers/media/pci/intel/ipu6/ |
| H A D | ipu6-cpd.c | 66 ipu6_cpd_metadata_get_cmpnt(struct ipu6_device *isp, const void *metadata, in ipu6_cpd_metadata_get_cmpnt() argument
80 return metadata + extn_size + idx * isp->cpd_metadata_cmpnt_size; in ipu6_cpd_metadata_get_cmpnt()
84 const void *metadata, in ipu6_cpd_metadata_cmpnt_version() argument
89 cmpnt = ipu6_cpd_metadata_get_cmpnt(isp, metadata, metadata_size, idx); in ipu6_cpd_metadata_cmpnt_version()
97 const void *metadata, in ipu6_cpd_metadata_get_cmpnt_id() argument
102 cmpnt = ipu6_cpd_metadata_get_cmpnt(isp, metadata, metadata_size, idx); in ipu6_cpd_metadata_get_cmpnt_id()
113 u64 *pkg_dir, const void *metadata, in ipu6_cpd_parse_module_data() argument
139 id = ipu6_cpd_metadata_get_cmpnt_id(isp, metadata, in ipu6_cpd_parse_module_data()
146 ver = ipu6_cpd_metadata_cmpnt_version(isp, metadata, in ipu6_cpd_parse_module_data()
210 /* Copy metadata after manifest */ in ipu6_cpd_create_pkg_dir()
[all …]
|
| /linux/fs/xfs/libxfs/ |
| H A D | xfs_metadir.c | 38 * Metadata Directory Tree
42 * deleting metadata inodes that live within a special metadata directory tree.
44 * This code does not manage the five existing metadata inodes: real time
45 * bitmap & summary; and the user, group, and quotas. All other metadata
48 * Callers wishing to create or hardlink a metadata inode must create an
51 * the update. Files in the metadata directory tree currently cannot be
54 * When the metadir feature is enabled, all metadata inodes must have the
55 * "metadata" inode flag set to prevent them from being exposed to the outside
58 * Callers must take the ILOCK of any inode in the metadata directory tree to
60 * or the MMAPLOCK since metadata inodes must not be exposed to user space.
[all …]
|
| H A D | xfs_health.h | 18 * shutdowns due to corrupt metadata.
20 * The online scrub feature evaluates the health of all filesystem metadata.
21 * When scrub detects corruption in a piece of metadata it will set the
27 * "checked" field tell us if a given piece of metadata has ever been examined,
31 * - checked && sick => metadata needs repair
32 * - checked && !sick => metadata is ok
34 * but the metadata has not been checked thoroughly
40 * general grouping of metadata.
59 /* Observable health issues for metadata spanning the entire filesystem. */
66 #define XFS_SICK_FS_METADIR (1 << 6) /* metadata directory tree */
[all …]
|
| /linux/tools/testing/kunit/ |
| H A D | kunit_json.py | 16 class Metadata: class
17 """Stores metadata about this run to include in get_json_result()."""
60 def get_json_result(test: Test, metadata: Metadata) -> str:
62 "arch": metadata.arch,
63 "defconfig": metadata.def_config,
64 "build_environment": metadata.build_dir,
50 get_json_result(test: Test, metadata: Metadata) global() argument
|
| /linux/Documentation/driver-api/dmaengine/ |
| H A D | client.rst | 167 **Optional: per descriptor metadata**
169 DMAengine provides two ways for metadata support.
173 The metadata buffer is allocated/provided by the client driver and it is
183 The metadata buffer is allocated/managed by the DMA driver. The client
185 the metadata and can directly update or read it.
187 Because the DMA driver manages the memory area containing the metadata,
191 metadata must not be accessed after issue_pending.
192 In other words: if the aim is to read back metadata after the transfer is
217 construct the metadata in the client's buffer
228 4. when the transfer is completed, the metadata should be available in the
[all …]
|
| /linux/tools/perf/tests/shell/ |
| H A D | test_bpf_metadata.sh | 2 # BPF metadata collection test
24 echo "Checking BPF metadata collection"
27 echo "Basic BPF metadata test [skipping - not supported]"
37 echo "Basic BPF metadata test [Failed record]"
66 echo "Basic BPF metadata test [Failed invalid output]"
70 echo "Basic BPF metadata test [Success]"
|
| /linux/fs/xfs/ |
| H A D | Kconfig | 31 by the V5 format, such as metadata checksumming, strengthened
32 metadata verification, and the ability to store timestamps past the
84 information as filesystem metadata and uses journaling to provide a
115 mechanism for ensuring data and metadata/log I/Os are completely
139 bool "XFS online metadata check support"
147 If you say Y here you will be able to check metadata on a
156 bool "XFS online metadata check usage data collection"
162 the online metadata check subsystem. This includes the number
171 bool "XFS online metadata repair support"
176 If you say Y here you will be able to repair metadata on a
[all …]
|