/kernel/linux/linux-5.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 …]
|
/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() 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 …]
|
/kernel/linux/linux-4.19/Documentation/device-mapper/ |
D | era.txt | 17 era <metadata dev> <origin dev> <block size> 19 metadata dev : fast device holding the persistent metadata 39 Create a clone of the metadata, to allow a userland process to read it. 44 Drop the metadata snapshot. 49 <metadata block size> <#used metadata blocks>/<#total metadata blocks> 50 <current era> <held metadata root | '-'> 52 metadata block size : Fixed block size for each metadata block in 54 #used metadata blocks : Number of metadata blocks used 55 #total metadata blocks : Total number of metadata blocks 57 held metadata root : The location, in blocks, of the metadata root [all …]
|
D | thin-provisioning.txt | 23 - Improve metadata resilience by storing metadata on a mirrored volume 26 - Improve performance by storing the metadata on SSD. 39 Userspace tools for checking and repairing the metadata have been fully 55 The pool device ties together the metadata volume and the data volume. 56 It maps I/O linearly to the data volume and updates the metadata via 67 Setting up a pool device requires a valid metadata device, and a 68 data device. If you do not have an existing metadata device you can 69 make one by zeroing the first 4k to indicate empty metadata. 73 The amount of metadata you need will vary according to how many blocks 75 less sharing than average you'll need a larger-than-average metadata device. [all …]
|
D | dm-zoned.txt | 26 internally for storing metadata and performaing reclaim operations. 39 metadata. 43 1) Metadata zones: these are conventional zones used to store metadata. 55 device being used. This allows reducing the amount of metadata needed to 58 The on-disk metadata format is as follows: 61 super block which describes the on disk amount and position of metadata 112 To protect metadata against corruption in case of sudden power loss or 113 system crash, 2 sets of metadata zones are used. One set, the primary 114 set, is used as the main metadata region, while the secondary set is 115 used as a staging area. Modified metadata is first written to the [all …]
|
D | cache.txt | 16 The target reuses the metadata library used in the thin-provisioning 49 3. A small metadata device - records which blocks are in the cache, 53 e.g. as a mirror for extra robustness. This metadata device may only 68 block sizes are bad because they increase the amount of metadata (both 79 the metadata. 124 Updating on-disk metadata 127 On-disk metadata is committed every time a FLUSH or FUA bio is written. 130 cache. If power is lost you may lose some recent writes. The metadata 172 cache <metadata dev> <cache dev> <origin dev> <block size> 176 metadata dev : fast device holding the persistent metadata [all …]
|
/kernel/linux/linux-5.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 …]
|
/kernel/linux/linux-5.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()
|
/kernel/linux/linux-4.19/Documentation/filesystems/ |
D | xfs-self-describing-metadata.txt | 13 Almost all metadata on XFS is dynamically allocated. The only fixed location 14 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all 15 other metadata structures need to be discovered by walking the filesystem 28 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata 39 One of the problems with the current metadata format is that apart from the 40 magic number in the metadata block, we have no other way of identifying what it 42 you can't look at a single metadata block in isolation and say "yes, it is 46 verification of metadata values, looking for values that are in range (and hence 53 Hence we need to record more information into the metadata to allow us to 54 quickly determine if the metadata is intact and can be ignored for the purpose [all …]
|
/kernel/linux/linux-5.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 …]
|
/kernel/linux/linux-4.19/samples/bpf/ |
D | xdp_sample_pkts_kern.c | 34 } __packed metadata; in xdp_sample_prog() local 51 metadata.cookie = 0xdead; in xdp_sample_prog() 52 metadata.pkt_len = (u16)(data_end - data); in xdp_sample_prog() 53 sample_size = min(metadata.pkt_len, SAMPLE_SIZE); in xdp_sample_prog() 57 &metadata, sizeof(metadata)); in xdp_sample_prog()
|
/kernel/linux/linux-5.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
|
/kernel/linux/linux-5.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
|
/kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
D | dev-meta.rst | 12 intended for transfer of metadata to userspace and control of that operation. 14 The metadata interface is implemented on video capture device nodes. The device 15 can be dedicated to metadata or can implement both video and metadata capture 21 Device nodes supporting the metadata interface set the ``V4L2_CAP_META_CAPTURE`` 24 ioctl. That flag means the device can capture metadata to memory. 32 The metadata device uses the :ref:`format` ioctls to select the capture format. 33 The metadata buffer content format is bound to that selected format. In addition 55 :ref:`four character code <v4l2-fourcc>`. V4L2 defines metadata formats
|
/kernel/linux/linux-5.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() 345 u32 metadata; in usb4_switch_drom_read_block() local 348 metadata = (dwords << USB4_DROM_SIZE_SHIFT) & USB4_DROM_SIZE_MASK; in usb4_switch_drom_read_block() 349 metadata |= (dwaddress << USB4_DROM_ADDRESS_SHIFT) & in usb4_switch_drom_read_block() 352 ret = usb4_switch_op_write_metadata(sw, metadata); in usb4_switch_drom_read_block() 512 u32 metadata; in usb4_switch_nvm_sector_size() local 523 ret = usb4_switch_op_read_metadata(sw, &metadata); in usb4_switch_nvm_sector_size() [all …]
|
/kernel/linux/linux-5.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 …]
|
/kernel/linux/linux-4.19/tools/perf/util/ |
D | cs-etm.c | 64 u64 **metadata; member 129 t_params[i].etmv4.reg_idr0 = etm->metadata[i][CS_ETMV4_TRCIDR0]; in cs_etm__dump_event() 130 t_params[i].etmv4.reg_idr1 = etm->metadata[i][CS_ETMV4_TRCIDR1]; in cs_etm__dump_event() 131 t_params[i].etmv4.reg_idr2 = etm->metadata[i][CS_ETMV4_TRCIDR2]; in cs_etm__dump_event() 132 t_params[i].etmv4.reg_idr8 = etm->metadata[i][CS_ETMV4_TRCIDR8]; in cs_etm__dump_event() 134 etm->metadata[i][CS_ETMV4_TRCCONFIGR]; in cs_etm__dump_event() 136 etm->metadata[i][CS_ETMV4_TRCTRACEIDR]; in cs_etm__dump_event() 243 zfree(&aux->metadata[i]); in cs_etm__free() 246 zfree(&aux->metadata); in cs_etm__free() 367 t_params[i].etmv4.reg_idr0 = etm->metadata[i][CS_ETMV4_TRCIDR0]; in cs_etm__alloc_queue() [all …]
|
/kernel/linux/linux-5.10/net/bridge/ |
D | br_vlan_tunnel.c | 66 struct metadata_dst *metadata = rtnl_dereference(vlan->tinfo.tunnel_dst); in __vlan_tunnel_info_add() local 70 if (metadata) in __vlan_tunnel_info_add() 73 metadata = __ip_tun_set_dst(0, 0, 0, 0, 0, TUNNEL_KEY, in __vlan_tunnel_info_add() 75 if (!metadata) in __vlan_tunnel_info_add() 78 metadata->u.tun_info.mode |= IP_TUNNEL_INFO_TX | IP_TUNNEL_INFO_BRIDGE; in __vlan_tunnel_info_add() 79 rcu_assign_pointer(vlan->tinfo.tunnel_dst, metadata); in __vlan_tunnel_info_add()
|
/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 …]
|
/kernel/linux/linux-4.19/Documentation/block/ |
D | data-integrity.txt | 4 Modern filesystems feature checksumming of data and metadata to 14 support for appending integrity metadata to an I/O. The integrity 15 metadata (or protection information in SCSI terminology) includes a 36 allow the operating system to interact with the integrity metadata 42 information to each sector. The data + integrity metadata is stored 49 encouraged them to allow separation of the data and integrity metadata 63 when writing and vice versa. This allows the integrity metadata to be 69 buffers and the integrity metadata. These two distinct buffers must 72 The separation of the data and integrity metadata buffers as well as 104 the kernel) is concerned, the integrity metadata is opaque information [all …]
|