/openbmc/linux/drivers/infiniband/hw/hns/ |
H A D | Kconfig | 3 tristate "HNS RoCE Driver" 8 This is a RoCE/RDMA driver for the Hisilicon RoCE engine. 13 bool "Hisilicon Hip08 Family RoCE support" 17 RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip08 SoC. 18 The RoCE engine is a PCI device.
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | configfs-rdma_cm | 20 will be initiated with this RoCE type as default. 21 The possible RoCE types are either "IB/RoCE v1" or "RoCE v2". 30 The possible RoCE TOS values are 0-255.
|
/openbmc/linux/drivers/infiniband/sw/rxe/ |
H A D | Kconfig | 3 tristate "Software RDMA over Ethernet (RoCE) driver" 12 standard Ethernet adapter to interoperate with a RoCE 14 Documentation on InfiniBand and RoCE can be downloaded at 25 To configure and work with soft-RoCE driver please use the 26 following wiki page under "configure Soft-RoCE (RXE)" section:
|
/openbmc/linux/Documentation/devicetree/bindings/infiniband/ |
H A D | hisilicon-hns-roce.txt | 1 Hisilicon RoCE DT description 3 Hisilicon RoCE engine is a part of network subsystem. 11 - reg: Physical base address of the RoCE driver and
|
/openbmc/bmcweb/redfish-core/include/generated/enums/ |
H A D | protocol.hpp | 31 RoCE, enumerator 76 {Protocol::RoCE, "RoCE"},
|
/openbmc/linux/Documentation/networking/devlink/ |
H A D | devlink-port.rst | 125 Users may also set the RoCE capability of the function using 177 RoCE capability setup 179 Not all PCI VFs/SFs require RoCE capability. 181 When RoCE capability is disabled, it saves system memory per PCI VF/SF. 183 When user disables RoCE capability for a VF/SF, user application cannot send or 184 receive any RoCE packets through this VF/SF and RoCE GID table for this PCI 187 When RoCE capability is disabled in the device using port function attribute, 190 - Get RoCE capability of the VF device:: 197 - Set RoCE capability of the VF device::
|
H A D | mlx5.rst | 22 If the device supports RoCE disablement, RoCE enablement state controls 23 device support for RoCE capability. Otherwise, the control occurs in the 24 driver stack. When RoCE is disabled at the driver level, only raw 89 with metadata. Metadata tagging must be enabled for multi-port RoCE, 94 1. HCA is in Dual/multi-port RoCE mode.
|
H A D | bnxt.rst | 82 - RoCE management firmware version
|
H A D | devlink-params.rst | 99 - Enable handling of RoCE traffic in the device.
|
H A D | devlink-info.rst | 193 RoCE firmware version which is responsible for handling roce
|
/openbmc/linux/drivers/infiniband/hw/qedr/ |
H A D | Kconfig | 3 tristate "QLogic RoCE driver"
|
/openbmc/linux/drivers/infiniband/hw/bnxt_re/ |
H A D | Kconfig | 8 RoCE HCAs. To compile this driver as a module, choose M here:
|
/openbmc/linux/drivers/infiniband/hw/irdma/ |
H A D | Kconfig | 12 that support E810 (iWARP/RoCE) and X722 (iWARP) network devices.
|
/openbmc/linux/net/smc/ |
H A D | Kconfig | 8 RDMA over Converged Ethernet (RoCE) technology to upgrade
|
/openbmc/linux/drivers/infiniband/sw/siw/ |
H A D | Kconfig | 13 (See also RXE which is a similar software driver for RoCE.)
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
H A D | switchdev.rst | 175 RoCE capability setup 177 Not all mlx5 PCI devices/SFs require RoCE capability. 179 When RoCE capability is disabled, it saves 1 Mbytes worth of system memory per 182 mlx5 driver support devlink port function attr mechanism to setup RoCE
|
H A D | counters.rst | 76 Ethernet) and RDMA/RoCE traffic counters. 781 RoCE/UD/RC traffic) [#accel]_. 786 RoCE/UD/RC traffic) [#accel]_. 791 RoCE/UD/RC traffic) [#accel]_. 796 RoCE/UD/RC traffic) [#accel]_. 801 RoCE/UD/RC traffic) [#accel]_. 806 RoCE/UD/RC traffic) [#accel]_. 811 RoCE/UD/RC traffic) [#accel]_. 816 RoCE/UD/RC traffic) [#accel]_.
|
H A D | kconfig.rst | 104 | Provides low-level InfiniBand/RDMA and `RoCE <https://enterprise-support.nvidia.com/s/article/…
|
/openbmc/linux/Documentation/ABI/stable/ |
H A D | sysfs-class-infiniband | 230 Description: The RoCE type of the associated GID resides at index <gid-index>. 231 This could either be "IB/RoCE v1" for IB and RoCE v1 based GIDs 232 or "RoCE v2" for RoCE v2 based GIDs. 363 <m>/pkey_idx/<n>: (RW) Writable except for RoCE pkeys. 599 sysfs interface for Emulex RoCE HCA Driver 771 sysfs interface for Broadcom NetXtreme-E RoCE driver
|
/openbmc/linux/drivers/block/rnbd/ |
H A D | README | 10 the server over RTRS protocol using the RDMA (InfiniBand, RoCE, iWARP)
|
/openbmc/linux/net/sunrpc/ |
H A D | Kconfig | 111 transports (InfiniBand, iWARP, or RoCE).
|
/openbmc/linux/drivers/nvme/host/ |
H A D | Kconfig | 54 the RDMA (Infiniband, RoCE, iWarp) transport. This allows you
|
/openbmc/linux/drivers/net/ethernet/hisilicon/ |
H A D | Kconfig | 97 This layer facilitates clients like ENET, RoCE and user-space ethernet
|
/openbmc/linux/drivers/infiniband/ulp/rtrs/ |
H A D | README | 7 between client and server machines using RDMA (InfiniBand, RoCE, iWarp)
|
/openbmc/qemu/docs/ |
H A D | rdma.txt | 37 RDMA currently comes in two flavors: both Ethernet based (RoCE, or RDMA
|