| /Linux-v5.10/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_surface.c | 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()
311 for (i = 0; i < srf->metadata.num_sizes; ++i) { 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()
204 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_create()
255 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_calculate_cfg()
291 bool metadata, in create_input_system_channel() argument
329 metadata ? cfg->metadata.bits_per_pixel : in create_input_system_channel()
[all …]
|
| /Linux-v5.10/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. 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 …]
|
| 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 …]
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 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
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
56 Hence we need to record more information into the metadata to allow us to
57 quickly determine if the metadata is intact and can be ignored for the purpose
[all …]
|
| D | squashfs.rst | 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.
199 stored compressed into metadata blocks. A second index table is used to
213 This table is stored compressed into metadata blocks. A second index table is
[all …]
|
| /Linux-v5.10/samples/bpf/ |
| D | xdp_sample_pkts_kern.c | 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/userspace-api/media/v4l/ |
| D | dev-meta.rst | 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.
39 The metadata buffer content format is bound to that selected format. In addition
62 :ref:`four character code <v4l2-fourcc>`. V4L2 defines metadata formats
|
| D | pixfmt-meta-d4xx.rst | 15 Intel D4xx (D435 and other) 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
29 Below are proprietary Microsoft style metadata types, used by D4xx cameras,
35 .. flat-table:: D4xx metadata
|
| /Linux-v5.10/drivers/net/ethernet/mellanox/mlx5/core/en_accel/ |
| D | ipsec_rxtx.h | 43 #define MLX5_IPSEC_METADATA_MARKER(metadata) (((metadata) >> 31) & 0x1) argument
44 #define MLX5_IPSEC_METADATA_SYNDROM(metadata) (((metadata) >> 24) & GENMASK(6, 0)) argument
45 #define MLX5_IPSEC_METADATA_HANDLE(metadata) ((metadata) & GENMASK(23, 0)) argument
|
| /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 …]
|
| /Linux-v5.10/drivers/md/ |
| D | dm-zoned-target.c | 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()
439 dmz_metadata_label(dmz->metadata), bio_op(bio)); in dmz_handle_bio()
[all …]
|
| 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-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/tools/perf/util/ |
| D | cs-etm.c | 64 u64 **metadata; member
134 u64 *metadata; in cs_etm__get_magic() local
140 metadata = inode->priv; in cs_etm__get_magic()
141 *magic = metadata[CS_ETM_MAGIC]; in cs_etm__get_magic()
148 u64 *metadata; in cs_etm__get_cpu() local
154 metadata = inode->priv; in cs_etm__get_cpu()
155 *cpu = (int)metadata[CS_ETM_CPU]; in cs_etm__get_cpu()
403 u64 **metadata = etm->metadata; in cs_etm__set_trace_param_etmv3() local
406 t_params[idx].etmv3.reg_ctrl = metadata[idx][CS_ETM_ETMCR]; in cs_etm__set_trace_param_etmv3()
407 t_params[idx].etmv3.reg_trc_id = metadata[idx][CS_ETM_ETMTRACEIDR]; in cs_etm__set_trace_param_etmv3()
[all …]
|
| /Linux-v5.10/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.10/include/trace/events/ |
| 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;
198 __assign_str(trap_name, metadata->trap_name);
199 __assign_str(trap_group_name, metadata->trap_group_name);
|
| /Linux-v5.10/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.10/include/uapi/linux/ |
| D | nvme_ioctl.h | 18 __u64 metadata; member
34 __u64 metadata; member
55 __u64 metadata; member
|
| /Linux-v5.10/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.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/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 …]
|
