Searched full:agents (Results 1 – 25 of 75) sorted by relevance
123
| /linux-6.12.1/drivers/net/ethernet/mellanox/mlx5/core/lib/ |
| D | hv_vhca.c | 12 struct mlx5_hv_vhca_agent *agents[MLX5_HV_VHCA_AGENT_MAX]; member
13 struct mutex agents_lock; /* Protect agents array */
81 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_invalidate_work()
120 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_agents_control()
138 struct mlx5_hv_vhca_agent *agent = hv_vhca->agents[i]; in mlx5_hv_vhca_capabilities()
220 hv_vhca->agents[MLX5_HV_VHCA_AGENT_CONTROL] = agent; in mlx5_hv_vhca_init()
233 agent = hv_vhca->agents[MLX5_HV_VHCA_AGENT_CONTROL]; in mlx5_hv_vhca_cleanup()
239 WARN_ON(hv_vhca->agents[i]); in mlx5_hv_vhca_cleanup()
270 if (hv_vhca->agents[type]) { in mlx5_hv_vhca_agent_create()
288 hv_vhca->agents[type] = agent; in mlx5_hv_vhca_agent_create()
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/perf/ |
| D | xgene-pmu.rst | 25 performance of a specific datapath. For example, agents of a L3 cache can be
27 masking the agents from which the request come from. If the bit with
31 counted for all agent requests (config1 = 0x0). For all the supported agents of
|
| D | arm-cmn.rst | 7 device ports to which various AMBA CHI agents are attached.
|
| /linux-6.12.1/Documentation/infiniband/ |
| D | user_mad.rst | 13 Creating MAD agents
29 Agents can be unregistered with the IB_USER_MAD_UNREGISTER_AGENT
30 ioctl. Also, all agents registered through a file descriptor will
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | hotplug.rst | 31 such programs are called "policy agents" here. Typically they involve
84 leverage USB module-init-tools support. Later agents might unload drivers.
92 files can be used by various user mode policy agents to make sure all the
|
| /linux-6.12.1/drivers/infiniband/sw/rdmavt/ |
| D | mad.c | 53 * rvt_create_mad_agents - create mad agents
102 * rvt_free_mad_agents - free up mad agents
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | connector.rst | 10 The Connector driver makes it easy to connect various agents using a
24 handling, etc... The Connector driver allows any kernelspace agents to use
|
| /linux-6.12.1/Documentation/driver-api/rapidio/ |
| D | rapidio.rst | 292 to indicate that enumeration is completed and agents are allowed to execute
295 The discovery process is performed by agents and is similar to the enumeration
297 without changes to the existing routing because agents only gather information
301 simultaneously by several agents. After initializing its RapidIO master port
|
| /linux-6.12.1/fs/sysfs/ |
| D | Kconfig | 16 Some system agents rely on the information in sysfs to operate.
|
| /linux-6.12.1/Documentation/devicetree/bindings/pci/ |
| D | fsl,pci.txt | 5 all mezzanines to be PCI-X Agents, but one per system may still
|
| /linux-6.12.1/Documentation/networking/ |
| D | netconsole.rst | 65 It also supports logging to multiple remote agents by specifying
66 parameters for the multiple agents separated by semicolons and the
287 so it is advised to explicitly specify the remote agents' MAC addresses
|
| D | tls-handshake.rst | 31 kernel consumer might require a TLS handshake. Handshake agents listen
|
| /linux-6.12.1/Documentation/scsi/ |
| D | smartpqi.rst | 78 agents, etc.
|
| D | hpsa.rst | 129 agents, etc. See cciss_vol_status at http://cciss.sf.net for some examples.
|
| /linux-6.12.1/drivers/dax/ |
| D | dax-private.h | 23 * @kref: to pin while other agents have a need to do lookups
|
| /linux-6.12.1/drivers/gpu/drm/i915/gt/ |
| D | intel_gt_mcr.c | 321 * firmware agents.
337 * driver threads, but also with hardware/firmware agents. A dedicated in intel_gt_mcr_lock()
408 * from other agents at those times, but it's possible that boot firmware
|
| D | intel_gt_pm.c | 228 * by other agents occur during driver load/resume process. in intel_gt_resume_early()
|
| /linux-6.12.1/Documentation/arch/powerpc/ |
| D | elf_hwcaps.rst | 176 accessed by other agents not running in this mode.
|
| /linux-6.12.1/Documentation/devicetree/bindings/mailbox/ |
| D | xlnx,zynqmp-ipi-mailbox.yaml | 11 messaging between two Xilinx Zynq UltraScale+ MPSoC IPI agents. Each IPI
|
| /linux-6.12.1/drivers/bus/ |
| D | omap_l3_smx.h | 194 /* offsets for l3 agents in order with the Flag status register */
|
| /linux-6.12.1/drivers/scsi/qla4xxx/ |
| D | ql4_nx.h | 135 /* This field defines PCI/X adr [25:20] of agents on the CRB */
203 /* This field defines CRB adr [31:20] of the agents */
|
| /linux-6.12.1/drivers/infiniband/core/ |
| D | user_mad.c | 625 * different agents unique, and allow routing responses back to the in ib_umad_write()
727 dev_notice(&file->port->dev, "%s: Max Agents (%u) reached\n", __func__, in ib_umad_reg_agent()
841 dev_notice(&file->port->dev, "%s: Max Agents (%u) reached\n", __func__, in ib_umad_reg_agent2()
|
| /linux-6.12.1/drivers/net/ethernet/qlogic/qlcnic/ |
| D | qlcnic_hdr.h | 127 /* This field defines PCI/X adr [25:20] of agents on the CRB */
228 /* This field defines CRB adr [31:20] of the agents */
|
| /linux-6.12.1/drivers/scsi/qla2xxx/ |
| D | qla_nx.h | 121 /* This field defines PCI/X adr [25:20] of agents on the CRB */
189 /* This field defines CRB adr [31:20] of the agents */
|
| /linux-6.12.1/arch/mips/include/asm/sibyte/ |
| D | bcm1480_scd.h | 307 * Register layout same as BCM1250, almost. The bus agents
|
123