| /linux/Documentation/networking/ |
| H A D | xdp-rx-metadata.rst | 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``.
42 Within an XDP frame, the metadata layout (accessed via ``xdp_buff``) is
[all …]
|
| H A D | xsk-tx-metadata.rst | 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.
61 only the first chunk should carry the metadata.
[all …]
|
| /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
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_MAGIC] == __perf_cs_etmv3_magic) { in cs_etm__init_pid_fmt()
212 val = metadata[CS_ETM_ETMCR]; in cs_etm__init_pid_fmt()
[all …]
|
| H A D | arm-spe.c | 99 u64 **metadata; member
327 if (!spe->metadata) in arm_spe__get_metadata_by_cpu()
340 return spe->metadata[0]; in arm_spe__get_metadata_by_cpu()
344 if (spe->metadata[i][ARM_SPE_CPU] == (u64)cpu) in arm_spe__get_metadata_by_cpu()
345 return spe->metadata[i]; in arm_spe__get_metadata_by_cpu()
939 u64 *metadata = in arm_spe__synth_memory_level() local
946 if (!metadata || in arm_spe__synth_memory_level()
947 !(metadata[ARM_SPE_CAP_EVENT_FILTER] & ARM_SPE_DATA_SNOOPED)) in arm_spe__synth_memory_level()
965 u64 *metadata = NULL; in arm_spe__synth_ds() local
977 metadata = arm_spe__get_metadata_by_cpu(spe, speq->cpu); in arm_spe__synth_ds()
[all …]
|
| H A D | bpf-event.h | 28 struct bpf_metadata *metadata; member
46 void bpf_metadata_free(struct bpf_metadata *metadata);
68 static inline void bpf_metadata_free(struct bpf_metadata *metadata __maybe_unused) in bpf_metadata_free()
|
| /linux/Documentation/admin-guide/device-mapper/ |
| 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 | 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 …]
|
| 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.
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
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
119 set, is used as the main metadata region, while the secondary set is
120 used as a staging area. Modified metadata is first written to the
[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-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 …]
|
| 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 …]
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 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
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
57 Hence we need to record more information into the metadata to allow us to
58 quickly determine if the metadata is intact and can be ignored for the purpose
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-generic.rst | 9 Generic line-based metadata formats
15 These generic line-based metadata formats define the memory layout of the data
16 without defining the format or meaning of the metadata itself.
23 The V4L2_META_FMT_GENERIC_8 format is a plain 8-bit metadata format. This format
26 Additionally it is used for 16 bits per Data Unit when two bytes of metadata are
31 Each cell is one byte. "M" denotes a byte of metadata.
56 V4L2_META_FMT_GENERIC_CSI2_10 contains 8-bit generic metadata packed in 10-bit
57 Data Units, with one padding byte after every four bytes of metadata. This
66 formats that pack two bytes of metadata into one Data Unit. Otherwise the
73 Each cell is one byte. "M" denotes a byte of metadata and "x" a byte of padding.
[all …]
|
| H A D | dev-meta.rst | 14 intended for transfer of metadata between the userspace and the hardware and
17 The metadata interface is implemented on video device nodes. The device can be
18 dedicated to metadata or can support both video and metadata as specified in its
24 Device nodes supporting the metadata capture interface set the
27 ioctl. That flag means the device can capture metadata to memory. Similarly,
28 device nodes supporting metadata output interface set the
31 metadata from memory.
39 The metadata device uses the :ref:`format` ioctls to select the capture format.
40 The metadata buffer content format is bound to that selected format. In addition
51 Devices that capture metadata by line have the struct v4l2_fmtdesc
[all …]
|
| /linux/drivers/md/ |
| H A D | dm-zoned-target.c | 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()
438 dmz_metadata_label(dmz->metadata), bio_op(bio)); in dmz_handle_bio()
[all …]
|
| H A D | dm-zoned-reclaim.c | 15 struct dmz_metadata *metadata; member
62 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_align_wp()
120 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_copy()
200 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_buf()
239 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_seq_data()
284 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_rnd_data()
342 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_empty()
366 struct dmz_metadata *zmd = zrc->metadata; in dmz_do_reclaim()
433 ret = dmz_flush_metadata(zrc->metadata); in dmz_do_reclaim()
448 struct dmz_metadata *zmd = zrc->metadata; in dmz_reclaim_percentage()
[all …]
|
| /linux/drivers/thunderbolt/ |
| H A D | usb4.c | 55 u32 *metadata, u8 *status, in usb4_native_switch_op() argument
62 if (metadata) { in usb4_native_switch_op()
63 ret = tb_sw_write(sw, metadata, TB_CFG_SWITCH, ROUTER_CS_25, 1); in usb4_native_switch_op()
94 if (metadata) { in usb4_native_switch_op()
95 ret = tb_sw_read(sw, metadata, TB_CFG_SWITCH, ROUTER_CS_25, 1); in usb4_native_switch_op()
109 static int __usb4_switch_op(struct tb_switch *sw, u16 opcode, u32 *metadata, in __usb4_switch_op() argument
126 ret = cm_ops->usb4_switch_op(sw, opcode, metadata, status, in __usb4_switch_op()
138 return usb4_native_switch_op(sw, opcode, metadata, status, tx_data, in __usb4_switch_op()
143 u32 *metadata, u8 *status) in usb4_switch_op() argument
145 return __usb4_switch_op(sw, opcode, metadata, status, NULL, 0, NULL, 0); in usb4_switch_op()
[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()
291 const void *metadata, u32 meta_size) in ipu6_cpd_validate_metadata() argument
[all …]
|
| /linux/tools/testing/kunit/ |
| H A D | kunit_json.py | 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,
|
| /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/tools/testing/selftests/bpf/progs/ |
| H A D | test_xdp_context_test_run.c | 9 __u32 *metadata = (void *)(long)xdp->data_meta; in xdp_context() local
12 if (metadata + 1 > data) in xdp_context()
14 ret = *metadata; in xdp_context()
|
| /linux/net/bridge/ |
| H A D | br_vlan_tunnel.c | 66 struct metadata_dst *metadata = rtnl_dereference(vlan->tinfo.tunnel_dst); in __vlan_tunnel_info_add() local
71 if (metadata) in __vlan_tunnel_info_add()
75 metadata = __ip_tun_set_dst(0, 0, 0, 0, 0, flags, key, 0); in __vlan_tunnel_info_add()
76 if (!metadata) in __vlan_tunnel_info_add()
79 metadata->u.tun_info.mode |= IP_TUNNEL_INFO_TX | IP_TUNNEL_INFO_BRIDGE; in __vlan_tunnel_info_add()
80 rcu_assign_pointer(vlan->tinfo.tunnel_dst, metadata); in __vlan_tunnel_info_add()
|
| /linux/include/trace/events/ |
| H A D | devlink.h | 179 const struct devlink_trap_metadata *metadata),
181 TP_ARGS(devlink, skb, metadata),
187 __string(trap_name, metadata->trap_name)
188 __string(trap_group_name, metadata->trap_group_name)
193 struct net_device *input_dev = metadata->input_dev;
|
| /linux/include/uapi/linux/ |
| H A D | nvme_ioctl.h | 18 __u64 metadata; member
34 __u64 metadata; member
55 __u64 metadata; member
81 __u64 metadata; member
|