Home
last modified time | relevance | path

Searched full:initiators (Results 1 – 25 of 42) sorted by relevance

12

/linux/Documentation/admin-guide/mm/
H A Dnumaperf.rst33 ranges accessible from one or more memory initiators.
35 When multiple memory initiators exist, they may not all have the same
39 is considered to be one of that target's local initiators, and given
41 local initiators, and any given initiator may have multiple local
44 To aid applications matching memory targets with their initiators, the
46 relationship for the access class "0" memory initiators and targets::
51 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
52 relative: /sys/devices/system/node/nodeY/access0/initiators/nodeX -> ../../nodeX
55 class. The target memory's initiators in a given class indicate the
60 The access class "1" is used to allow differentiation between initiators
[all …]
/linux/Documentation/block/
H A Dpr.rst8 access to block devices to specific initiators in a shared storage
34 Only initiators with a registered key can write to the device,
38 Only initiators with a registered key can access the device.
42 Only initiators with a registered key can write to the device,
44 All initiators with a registered key are considered reservation
50 Only initiators with a registered key can access the device.
51 All initiators with a registered key are considered reservation
/linux/Documentation/devicetree/bindings/arm/tegra/
H A Dnvidia,tegra194-cbb.yaml16 initiators and targets using different bridges like AXIP2P, AXI2APB.
31 - For other initiators, the ERD is disabled. So, the access issuing
33 In addition, an interrupt is also generated to CCPLEX. These initiators
/linux/Documentation/devicetree/bindings/arm/omap/
H A Ddmm.txt5 accesses such as priority generation amongst initiators, configuration of SDRAM
7 translation for initiators which need contiguous dma bus addresses.
/linux/include/soc/tegra/
H A Dbpmp-abi.h418 * * Initiators: Any
428 * * Initiators: Any
474 * * Initiators: CCPLEX
500 * * Initiators: Any
538 * * Initiators: Any
689 * * Initiators: Any
866 * * Initiators: Any
966 * * Initiators: Any
1090 * * Initiators: Any
1445 * * Initiators: Any
[all …]
/linux/Documentation/admin-guide/device-mapper/
H A Dswitch.rst23 spreading are hidden from initiators connected to this storage system.
34 the storage group and initiators. In a multipathing configuration, it
/linux/drivers/acpi/numa/
H A DKconfig13 register memory initiators with their targets, and export
/linux/Documentation/driver-api/cxl/platform/acpi/
H A Dslit.rst8 accessor and memory nodes. Node without initiators (cpus) are infinitely (FF)
/linux/arch/arm/mach-omap2/
H A Dsram.c116 * device allows ARM11 but not other initiators for full size. This
122 /* RAMFW: R/W access to all initiators for all qualifier sets */ in is_sram_locked()
H A Domap4-common.c102 * The work-around for this errata needs all the initiators connected
108 * IO barrier ensure that there is no synchronisation loss on initiators
H A Domap_hwmod.h204 * omap_hwmod_ocp_if.user bits: these indicate the initiators that use this
230 * @user: initiators using this interface (see OCP_USER_* macros above)
/linux/drivers/base/
H A Dnode.c99 static const struct attribute_group initiators = { variable
100 .name = "initiators",
110 &initiators,
234 "initiators")) { in node_set_perf_attrs()
788 ret = sysfs_add_link_to_group(&target->dev.kobj, "initiators", in register_memory_node_under_compute_node()
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-cxl584 /sys/devices/system/node/nodeX/accessY/initiators/read_bandwidth or
585 /sys/devices/system/node/nodeX/accessY/initiators/write_bandwidth.
601 /sys/devices/system/node/nodeX/accessY/initiators/read_latency or
602 /sys/devices/system/node/nodeX/accessY/initiators/write_latency.
H A Dsysfs-class-scsi_host112 tools for their SGPIO initiators.
/linux/include/linux/fsl/bestcomm/
H A Dbestcomm_priv.h159 /* Initiators number */
195 /* Initiators priorities */
/linux/Documentation/target/
H A Dtarget-export-device77 # Allow write access for non authenticated initiators
H A Dtcmu-design.rst54 target then serves as a translator, allowing initiators to store data
/linux/include/target/iscsi/
H A Discsi_target_core.h72 * as a workaround for non RFC compliant initiators,that do not propose,
/linux/drivers/scsi/libfc/
H A Dfc_disc.c11 * This block discovers all FC-4 remote ports, including FCP initiators. It
/linux/include/scsi/
H A Dscsi_host.h884 * All DIX-capable initiators must support the T10-mandated CRC
/linux/drivers/target/
H A Dtarget_core_device.c544 * Update LUN maps for dynamically added initiators when in core_dev_add_lun()
H A Dtarget_core_iblock.c947 * The block layer pr_ops do not support passing in initiators so in iblock_pr_report_caps()
/linux/scripts/
H A Dspelling.txt877 initators||initiators
/linux/drivers/vhost/
H A Dscsi.c3 * Vhost kernel TCM fabric driver for virtio SCSI initiators
1250 * Initiators normally just put the virtio_scsi_cmd_resp in the first in vhost_scsi_setup_resp_iovs()
/linux/include/linux/
H A Dnvme-fc-driver.h886 * change notifications to NVME initiators. The RSCN notifications

12