Home
last modified time | relevance | path

Searched refs:IB (Results 1 – 25 of 25) sorted by relevance

/Linux-v5.10/Documentation/infiniband/
Dipoib.rst40 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
Dopa_vnic.rst107 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 | |
Duser_verbs.rst6 enables direct userspace access to IB hardware via "verbs," as
36 Since creation and destruction of all IB resources is done by
Dcore_locking.rst57 The IB midlayer does not perform any serialization of function calls.
111 An upper level protocol consumer may begin using an IB device as
/Linux-v5.10/drivers/infiniband/hw/mlx5/
DKconfig7 Mellanox Connect-IB PCI Express host channel adapters (HCAs).
9 IP-over-IB or SRP with these devices.
/Linux-v5.10/Documentation/admin-guide/cgroup-v1/
Drdma.rst19 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.10/drivers/infiniband/hw/hfi1/
Dtrace.h53 packettype_name(IB), \
/Linux-v5.10/drivers/infiniband/ulp/ipoib/
DKconfig7 transports IP packets over InfiniBand so you can use your IB
39 information about IB multicast groups used by the IPoIB
/Linux-v5.10/drivers/infiniband/ulp/opa_vnic/
DKconfig9 data path and IB MAD for the control path.
/Linux-v5.10/drivers/infiniband/hw/mlx4/
DKconfig11 IP-over-IB or SRP with these devices.
/Linux-v5.10/arch/arm/boot/dts/
Dgemini-nas4220b.dts3 * Device Tree file for the Gemini-based Raidsonic NAS IB-4220-B
12 model = "Raidsonic NAS IB-4220-B";
Dkirkwood-ib62x0.dts8 model = "RaidSonic ICY BOX IB-NAS62x0 (Rev B)";
/Linux-v5.10/Documentation/networking/
Drds.rst27 as IB.
39 transport has to be IP-based. In fact, RDS over IB uses a
40 reliable IB connection; the IP address is used exclusively to
226 One might think that with reliable IB connections you wouldn't need
227 to ack messages that have been received. The problem is that IB
244 RDS's IB transport uses a credit-based mechanism to verify that
279 As mentioned above, RDS is not IB-specific. Its code is divided
285 The transport layer handles the details of the transport. The IB
/Linux-v5.10/net/sched/
Dsch_qfq.c123 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.10/Documentation/admin-guide/nfs/
Dnfs-rdma.rst41 Testing has been performed using several Mellanox-based IB cards, the
118 InfiniBand support is required for all RDMA devices (IB, iWARP, etc.)].
120 Enable the appropriate IB HCA support (mlx4, mthca, ehca, ipath, etc.) or
173 running on the network. If your IB switch has an embedded SM, you can
187 assumes you have two IB hosts named host1 and host2):
/Linux-v5.10/Documentation/ABI/stable/
Dsysfs-class-infiniband27 node's hostname, so that IB network management software can tie
231 This could either be "IB/RoCE v1" for IB and RoCE v1 based GIDs
249 ibdev: (RO) Show Infiniband (IB) device name
271 ibdev: (RO) Display Infiniband (IB) device name
273 abi_version: (RO) Show ABI version of IB device specific
287 sysfs interface for Mellanox IB HCA low-level driver (mthca)
307 sysfs interface for Mellanox ConnectX HCA IB driver (mlx4)
426 sysfs interface for Intel IB driver qib
543 sysfs interface for Mellanox Connect-IB HCA driver mlx5
Dsysfs-driver-ib_srp66 IB RC retry count.
/Linux-v5.10/Documentation/ABI/testing/
Dconfigfs-rdma_cm21 The possible RoCE types are either "IB/RoCE v1" or "RoCE v2".
/Linux-v5.10/drivers/platform/mellanox/
DKconfig24 cables and fans on the wide range Mellanox IB and Ethernet systems.
/Linux-v5.10/drivers/infiniband/
DKconfig12 Core support for InfiniBand (IB). Make sure to also select
/Linux-v5.10/drivers/net/ethernet/mellanox/mlx5/core/
DKconfig17 Connect-IB cards by Mellanox Technologies.
/Linux-v5.10/drivers/eisa/
Deisa.ids537 HWP0C70 "HP-IB Host Adapter"
543 HWP1450 "HP HP-IB Interface board (82335A)"
/Linux-v5.10/init/
DKconfig1023 Provides enforcement of RDMA resources defined by IB stack.
/Linux-v5.10/Documentation/admin-guide/
Dcgroup-v2.rst2097 for a RDMA/IB device.
/Linux-v5.10/
DMAINTAINERS11247 MELLANOX MLX4 IB driver
11269 MELLANOX MLX5 IB driver