Searched refs:subfunction (Results 1 – 11 of 11) sorted by relevance
| /Linux-v6.6/Documentation/networking/devlink/ |
| D | devlink-port.rst | 39 subfunction (SF).
303 SRIOV VFs, a subfunction doesn't require its own PCI virtual function.
304 A subfunction communicates with the hardware through the parent PCI function.
306 To use a subfunction, 3 steps setup sequence is followed:
308 1) create - create a subfunction;
309 2) configure - configure subfunction attributes;
310 3) deploy - deploy the subfunction;
313 User performs setup on the subfunction management device.
317 A subfunction is created using a devlink port interface. A user adds the
318 subfunction by adding a devlink port of subfunction flavour. The devlink
[all …]
|
| /Linux-v6.6/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | switchdev.rst | 70 mlx5 supports subfunction management using devlink port (see :ref:`Documentation/networking/devlink…
72 A subfunction has its own function capabilities and its own resources. This
73 means a subfunction has its own dedicated queues (txq, rxq, cq, eq). These
76 When a subfunction is RDMA capable, it has its own QP1, GID table, and RDMA
79 A subfunction has a dedicated window in PCI BAR space that is not shared
81 devices (netdev, rdma, vdpa, etc.) of the subfunction accesses only assigned
84 A subfunction supports eswitch representation through which it supports tc
86 the subfunction port.
120 | subfunction | | +---------------+ | subfunction |
121 | management driver|----- | subfunction |---| driver |
[all …]
|
| D | kconfig.rst | 116 | Build support for subfunction.
118 | will enable support for creating subfunction devices.
123 | Build support for subfuction port in the NIC. A Mellanox subfunction
124 | port is managed through devlink. A subfunction supports RDMA, netdevice
|
| /Linux-v6.6/Documentation/devicetree/bindings/leds/ |
| D | leds-mt6323.txt | 3 MT6323 LED controller is subfunction provided by MT6323 PMIC, so the LED
6 using shared bus called PMIC wrapper for each subfunction to access remote
|
| /Linux-v6.6/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | Kconfig | 176 bool "Mellanox Technologies subfunction device support using auxiliary device"
179 Build support for subfuction device in the NIC. A Mellanox subfunction
188 Build support for subfuction port in the NIC. A Mellanox subfunction
189 port is managed through devlink. A subfunction supports RDMA, netdevice
|
| /Linux-v6.6/sound/firewire/ |
| D | fcp.h | 25 unsigned int subunit_id, unsigned int subfunction,
|
| D | fcp.c | 140 unsigned int subunit_id, unsigned int subfunction, in avc_general_get_plug_info() argument
158 buf[3] = 0xff & subfunction; in avc_general_get_plug_info()
|
| /Linux-v6.6/Documentation/virt/kvm/devices/ |
| D | vm.rst | 147 A subfunction block is only valid if KVM_S390_VM_CPU_MACHINE contains the
149 indicates subfunctions via a "query subfunction", the response block is
151 indicates subfunctions via a "test bit" mechanism, the subfunction codes are
175 :Parameters: address of a buffer to load the subfunction blocks from.
186 The kernel uses the configured subfunction blocks for indication to
187 the guest. A subfunction block will only be used if the associated STFL(E) bit
198 :Parameters: address of a buffer to store/load the subfunction blocks from.
|
| /Linux-v6.6/arch/x86/kernel/ |
| D | vm86_32.c | 167 static int do_vm86_irq_handling(int subfunction, int irqnumber);
799 static int do_vm86_irq_handling(int subfunction, int irqnumber) in do_vm86_irq_handling() argument
802 switch (subfunction) { in do_vm86_irq_handling()
|
| /Linux-v6.6/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 44 General register 1 contains the virtio subfunction code. Supported
|
| /Linux-v6.6/Documentation/networking/ |
| D | representors.rst | 46 these administrative privileges instead to a VF or SF (subfunction).
|
