Home
last modified time | relevance | path

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

/linux-4.4.14/drivers/infiniband/hw/mlx5/
DKconfig2 tristate "Mellanox Connect-IB HCA support"
6 Mellanox Connect-IB PCI Express host channel adapters (HCAs).
8 IP-over-IB or SRP with these devices.
/linux-4.4.14/Documentation/infiniband/
Dipoib.txt36 In datagram mode, the IB UD (Unreliable Datagram) transport is used
37 and so the interface MTU has is equal to the IB L2 MTU minus the
38 IPoIB encapsulation header (4 bytes). For example, in a typical IB
41 In connected mode, the IB RC (Reliable Connected) transport is used.
42 Connected mode takes advantage of the connected nature of the IB
55 If the IB HW supports IPoIB stateless offloads, IPoIB advertises
67 If the underlying IB device supports CQ event moderation, one can
Duser_verbs.txt4 enables direct userspace access to IB hardware via "verbs," as
32 Since creation and destruction of all IB resources is done by
Dcore_locking.txt57 The IB midlayer does not perform any serialization of function calls.
109 An upper level protocol consumer may begin using an IB device as
/linux-4.4.14/drivers/net/ethernet/mellanox/mlx5/core/
DKconfig6 tristate "Mellanox Technologies ConnectX-4 and Connect-IB core driver"
11 Connect-IB cards by Mellanox Technologies.
/linux-4.4.14/drivers/scsi/pm8001/
Dpm8001_defs.h97 #define IB (USI_MAX_MEMCNT_BASE + 1) macro
98 #define CI (IB + PM8001_MAX_SPCV_INB_NUM)
Dpm8001_init.c287 pm8001_ha->memoryMap.region[IB+i].num_elements = in pm8001_alloc()
289 pm8001_ha->memoryMap.region[IB+i].element_size = 128; in pm8001_alloc()
290 pm8001_ha->memoryMap.region[IB+i].total_len = in pm8001_alloc()
292 pm8001_ha->memoryMap.region[IB+i].alignment = 128; in pm8001_alloc()
294 pm8001_ha->memoryMap.region[IB+i].num_elements = in pm8001_alloc()
296 pm8001_ha->memoryMap.region[IB+i].element_size = 64; in pm8001_alloc()
297 pm8001_ha->memoryMap.region[IB+i].total_len = in pm8001_alloc()
299 pm8001_ha->memoryMap.region[IB+i].alignment = 64; in pm8001_alloc()
Dpm8001_ctl.c328 memoryMap.region[IB].virt_ptr + \ in pm8001_ctl_ib_queue_log_show()
Dpm80xx_hwi.c498 pm8001_ha->memoryMap.region[IB + i].phys_addr_hi; in init_default_table_values()
500 pm8001_ha->memoryMap.region[IB + i].phys_addr_lo; in init_default_table_values()
502 (u8 *)pm8001_ha->memoryMap.region[IB + i].virt_ptr; in init_default_table_values()
504 pm8001_ha->memoryMap.region[IB + i].total_len; in init_default_table_values()
Dpm8001_hwi.c226 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-4.4.14/drivers/infiniband/ulp/ipoib/
DKconfig6 transports IP packets over InfiniBand so you can use your IB
38 information about IB multicast groups used by the IPoIB
/linux-4.4.14/drivers/staging/rdma/hfi1/
DTODO4 - Remove software processing of IB protocol and place in library for use
Dtrace.h71 packettype_name(IB), \
/linux-4.4.14/drivers/infiniband/hw/mlx4/
DKconfig10 IP-over-IB or SRP with these devices.
/linux-4.4.14/Documentation/networking/
Drds.txt22 as IB. Work is in progress to support RDS over iWARP, and using DCE to
35 transport has to be IP-based. In fact, RDS over IB uses a
36 reliable IB connection; the IP address is used exclusively to
199 One might think that with reliable IB connections you wouldn't need
200 to ack messages that have been received. The problem is that IB
217 RDS's IB transport uses a credit-based mechanism to verify that
252 As mentioned above, RDS is not IB-specific. Its code is divided
258 The transport layer handles the details of the transport. The IB
/linux-4.4.14/Documentation/filesystems/nfs/
Dnfs-rdma.txt51 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-4.4.14/drivers/staging/rdma/ipath/
DKconfig6 IB host channel adapter (model QHT7140),
/linux-4.4.14/net/sched/
Dsch_qfq.c126 enum qfq_state { ER, IR, EB, IB, QFQ_MAX_STATE }; enumerator
810 qfq_move_groups(q, mask, IB, IR); in qfq_unblock_groups()
838 qfq_move_groups(q, mask, IB, EB); in qfq_make_eligible()
983 ineligible = q->bitmaps[IR] | q->bitmaps[IB]; in qfq_update_eligible()
1307 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_schedule_agg()
1385 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_deactivate_agg()
1395 qfq_move_groups(q, mask, IB, IR); in qfq_deactivate_agg()
1405 __clear_bit(grp->index, &q->bitmaps[IB]); in qfq_deactivate_agg()
/linux-4.4.14/arch/arm/boot/dts/
Dkirkwood-ib62x0.dts7 model = "RaidSonic ICY BOX IB-NAS62x0 (Rev B)";
/linux-4.4.14/drivers/infiniband/
DKconfig9 Core support for InfiniBand (IB). Make sure to also select
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-driver-ib_srp65 IB RC retry count.
/linux-4.4.14/drivers/eisa/
Deisa.ids537 HWP0C70 "HP-IB Host Adapter"
543 HWP1450 "HP HP-IB Interface board (82335A)"
/linux-4.4.14/
DMAINTAINERS7063 Mellanox MLX5 IB driver