/Linux-v5.4/Documentation/infiniband/ |
D | ipoib.rst | 40 In datagram mode, the IB UD (Unreliable Datagram) transport is used 41 and so the interface MTU has is equal to the IB L2 MTU minus the 42 IPoIB encapsulation header (4 bytes). For example, in a typical IB 45 In connected mode, the IB RC (Reliable Connected) transport is used. 46 Connected mode takes advantage of the connected nature of the IB 60 If the IB HW supports IPoIB stateless offloads, IPoIB advertises 73 If the underlying IB device supports CQ event moderation, one can
|
D | opa_vnic.rst | 107 The support has been added for IB device to allocate and free the RDMA 123 registers itself with IB core as an IB client and interfaces with the 124 IB MAD stack. It exchanges the management information with the Ethernet 136 | IB MAD | | Network | 151 | IB core | |
|
D | user_verbs.rst | 6 enables direct userspace access to IB hardware via "verbs," as 36 Since creation and destruction of all IB resources is done by
|
D | core_locking.rst | 59 The IB midlayer does not perform any serialization of function calls. 113 An upper level protocol consumer may begin using an IB device as
|
/Linux-v5.4/drivers/infiniband/hw/mlx5/ |
D | Kconfig | 7 Mellanox Connect-IB PCI Express host channel adapters (HCAs). 9 IP-over-IB or SRP with these devices.
|
/Linux-v5.4/drivers/scsi/pm8001/ |
D | pm8001_defs.h | 97 #define IB (USI_MAX_MEMCNT_BASE + 1) macro 98 #define CI (IB + PM8001_MAX_SPCV_INB_NUM)
|
D | pm8001_init.c | 284 pm8001_ha->memoryMap.region[IB+i].num_elements = in pm8001_alloc() 286 pm8001_ha->memoryMap.region[IB+i].element_size = 128; in pm8001_alloc() 287 pm8001_ha->memoryMap.region[IB+i].total_len = in pm8001_alloc() 289 pm8001_ha->memoryMap.region[IB+i].alignment = 128; in pm8001_alloc() 291 pm8001_ha->memoryMap.region[IB+i].num_elements = in pm8001_alloc() 293 pm8001_ha->memoryMap.region[IB+i].element_size = 64; in pm8001_alloc() 294 pm8001_ha->memoryMap.region[IB+i].total_len = in pm8001_alloc() 296 pm8001_ha->memoryMap.region[IB+i].alignment = 64; in pm8001_alloc()
|
D | pm8001_ctl.c | 380 memoryMap.region[IB].virt_ptr + \ in pm8001_ctl_ib_queue_log_show()
|
D | pm8001_hwi.c | 226 pm8001_ha->memoryMap.region[IB + i].phys_addr_hi; in init_default_table_values() 228 pm8001_ha->memoryMap.region[IB + i].phys_addr_lo; in init_default_table_values() 230 (u8 *)pm8001_ha->memoryMap.region[IB + i].virt_ptr; in init_default_table_values() 232 pm8001_ha->memoryMap.region[IB + i].total_len; in init_default_table_values()
|
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
D | rdma.rst | 19 RDMA controller allows user to limit RDMA/IB specific resources that a given 70 (b) No resource limits were configured, but IB/RDMA stack tries to 81 IB stack honors limits enforced by the rdma controller. When application 82 query about maximum resource limits of IB device, it returns minimum of 84 IB device.
|
/Linux-v5.4/drivers/infiniband/hw/hfi1/ |
D | trace.h | 53 packettype_name(IB), \
|
/Linux-v5.4/drivers/infiniband/ulp/ipoib/ |
D | Kconfig | 7 transports IP packets over InfiniBand so you can use your IB 39 information about IB multicast groups used by the IPoIB
|
/Linux-v5.4/drivers/infiniband/ulp/opa_vnic/ |
D | Kconfig | 9 data path and IB MAD for the control path.
|
/Linux-v5.4/drivers/infiniband/hw/mlx4/ |
D | Kconfig | 11 IP-over-IB or SRP with these devices.
|
/Linux-v5.4/arch/arm/boot/dts/ |
D | gemini-nas4220b.dts | 3 * Device Tree file for the Gemini-based Raidsonic NAS IB-4220-B 12 model = "Raidsonic NAS IB-4220-B";
|
D | kirkwood-ib62x0.dts | 8 model = "RaidSonic ICY BOX IB-NAS62x0 (Rev B)";
|
/Linux-v5.4/Documentation/filesystems/nfs/ |
D | nfs-rdma.txt | 51 Testing has been performed using several Mellanox-based IB cards, the 125 InfiniBand support is required for all RDMA devices (IB, iWARP, etc.)]. 127 Enable the appropriate IB HCA support (mlx4, mthca, ehca, ipath, etc.) or 176 running on the network. If your IB switch has an embedded SM, you can 188 assumes you have two IB hosts named host1 and host2):
|
/Linux-v5.4/net/sched/ |
D | sch_qfq.c | 123 enum qfq_state { ER, IR, EB, IB, QFQ_MAX_STATE }; enumerator 789 qfq_move_groups(q, mask, IB, IR); in qfq_unblock_groups() 817 qfq_move_groups(q, mask, IB, EB); in qfq_make_eligible() 962 ineligible = q->bitmaps[IR] | q->bitmaps[IB]; in qfq_update_eligible() 1295 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_schedule_agg() 1373 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_deactivate_agg() 1383 qfq_move_groups(q, mask, IB, IR); in qfq_deactivate_agg() 1393 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_deactivate_agg()
|
/Linux-v5.4/Documentation/networking/ |
D | rds.txt | 22 as IB. 33 transport has to be IP-based. In fact, RDS over IB uses a 34 reliable IB connection; the IP address is used exclusively to 212 One might think that with reliable IB connections you wouldn't need 213 to ack messages that have been received. The problem is that IB 230 RDS's IB transport uses a credit-based mechanism to verify that 265 As mentioned above, RDS is not IB-specific. Its code is divided 271 The transport layer handles the details of the transport. The IB
|
/Linux-v5.4/Documentation/ABI/stable/ |
D | sysfs-class-infiniband | 25 node's hostname, so that IB network management software can tie 230 This could either be "IB/RoCE v1" for IB and RoCE v1 based GIDs 247 ibdev: (RO) Show Infiniband (IB) device name 266 (RO) Display Infiniband (IB) device name 284 ibdev: (RO) Display Infiniband (IB) device name 286 abi_version: (RO) Show ABI version of IB device specific 299 sysfs interface for Mellanox IB HCA low-level driver (mthca) 336 sysfs interface for Mellanox ConnectX HCA IB driver (mlx4) 447 sysfs interface for Intel IB driver qib 558 sysfs interface for Mellanox Connect-IB HCA driver mlx5
|
D | sysfs-driver-ib_srp | 65 IB RC retry count.
|
/Linux-v5.4/Documentation/ABI/testing/ |
D | configfs-rdma_cm | 21 The possible RoCE types are either "IB/RoCE v1" or "RoCE v2".
|
/Linux-v5.4/drivers/platform/mellanox/ |
D | Kconfig | 24 cables and fans on the wide range Mellanox IB and Ethernet systems.
|
/Linux-v5.4/drivers/infiniband/ |
D | Kconfig | 12 Core support for InfiniBand (IB). Make sure to also select
|
/Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
D | Kconfig | 17 Connect-IB cards by Mellanox Technologies.
|