| /freebsd/sys/contrib/device-tree/Bindings/display/mediatek/ |
| H A D | mediatek,rdma.yaml | 4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,rdma.yaml#
14 Mediatek Read Direct Memory Access(RDMA) component used to read the
18 RDMA device node must be siblings to the central MMSYS_CONFIG node.
27 - mediatek,mt2701-disp-rdma
28 - mediatek,mt8173-disp-rdma
29 - mediatek,mt8183-disp-rdma
30 - mediatek,mt8195-disp-rdma
33 - mediatek,mt8188-disp-rdma
34 - const: mediatek,mt8195-disp-rdma
37 - mediatek,mt7623-disp-rdma
[all …]
|
| H A D | mediatek,disp.txt | 32 "mediatek,<chip>-disp-rdma" - read DMA / line buffer
39 "mediatek,<chip>-disp-merge" - merge streams from two RDMA sources
61 "mediatek,<chip>-disp-rdma"
70 Optional properties (RDMA function blocks):
71 - mediatek,rdma-fifo-size: rdma fifo size may be different even in same SOC, add this
72 property to the corresponding rdma
74 mediatek,rdma-fifo-size of mt8173-rdma0 is 8K
75 mediatek,rdma-fifo-size of mt8183-rdma0 is 5K
76 mediatek,rdma-fifo-size of mt8183-rdma1 is 2K
107 rdma0: rdma@1400e000 {
[all …]
|
| H A D | mediatek,mdp-rdma.yaml | 4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,mdp-rdma.yaml#
7 title: MediaTek MDP RDMA
14 The MediaTek MDP RDMA stands for Read Direct Memory Access.
18 RDMA device node must be siblings to the central MMSYS_CONFIG node.
24 const: mediatek,mt8195-vdo1-rdma
37 - description: RDMA Clock
79 rdma@1c104000 {
80 compatible = "mediatek,mt8195-vdo1-rdma";
|
| /freebsd/sys/dev/ice/ |
| H A D | ice_rdma.c | 34 * @brief RDMA client driver interface
36 * Functions to interface with the RDMA client driver, for enabling RMDA
39 * The RDMA client interface is based on a simple kobject interface which is
43 * the client RDMA driver provides the irdma_if.m interface methods as an
46 * The initial connection between drivers is done via the RDMA client driver
58 * @brief global RDMA driver state
60 * Contains global state the driver uses to connect to a client RDMA interface
76 * RDMA Device Interface prototypes
91 * @brief RDMA driver interface methods
93 * Kobject methods implementing the driver-side interface for the RDMA pee
[all...] |
| H A D | irdma_if.m | 33 * @brief RDMA client kobject interface
35 * KOBject methods implemented by the RDMA client driver. These functions will
36 * be called from the ice driver to notify the RDMA client driver of device
44 * probe - Notify the RDMA client driver that a peer device has been created
45 * @peer: the RDMA peer structure
47 * Called by the ice driver during attach to notify the RDMA client driver
56 * open - Notify the RDMA client driver that a peer device has been opened
57 * @peer: the RDMA peer structure
59 * Called by the ice driver during the if_init routine to notify the RDMA
68 * close - Notify the RDMA clien
[all...] |
| H A D | irdma_di_if.m | 33 * @brief RDMA client kobject driver interface
36 * by the RDMA client driver to connect with the ice driver and request
37 * operations or notify the driver of RDMA events.
45 * @peer: the RDMA peer structure
47 * Called by the RDMA client driver to request a reset of the ice device.
55 * msix_init - Initialize MSI-X resources for the RDMA driver
56 * @peer: the RDMA peer structure
59 * Called by the RDMA client driver to request initialization of the MSI-X
60 * resources used for RDMA functionality.
69 * qset_register_request - RDMA clien
[all...] |
| H A D | ice_rdma.h | 34 * @brief header file for RDMA client interface functions
37 * RDMA client interface driver.
46 * The RDMA client interface version is used to help determine
74 * Defines the maximum number of MSI-X vectors that an RDMA interface will
82 * @brief RDMA information from the client driver
84 * The RDMA client driver will fill in this structure and pass its contents
94 * of the RDMA driver will fail.
121 * @brief MSI-X mapping requested by the peer RDMA driver
123 * Defines a mapping for MSI-X vectors being requested by the peer RDMA driver
136 * @brief RDMA MS
[all...] |
| H A D | ice_rdma_internal.h | 37 * RDMA driver interface. Functions and definitions in this file are not
38 * shared with the RDMA client driver.
48 /* Global sysctl variable indicating if the RDMA client interface is enabled */
53 * @brief RDMA peer list node
61 * list node of the RDMA entry
78 * @brief Head list structure for the RDMA entry list
80 * Type defining the head of the linked list of RDMA entries.
86 * @brief global driver state for RDMA
99 * list of RDMA entries
|
| /freebsd/sys/contrib/device-tree/Bindings/media/ |
| H A D | mediatek,mdp3-rdma.yaml | 4 $id: http://devicetree.org/schemas/media/mediatek,mdp3-rdma.yaml#
14 MediaTek Read Direct Memory Access(RDMA) component used to do read DMA.
25 - mediatek,mt8183-mdp3-rdma
26 - mediatek,mt8188-mdp3-rdma
27 - mediatek,mt8195-mdp3-rdma
28 - mediatek,mt8195-vdo1-rdma
30 - const: mediatek,mt8188-vdo1-rdma
31 - const: mediatek,mt8195-vdo1-rdma
68 - description: RDMA clock
77 - description: used for 1st data pipe from RDMA
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_cm.7 | 4 rdma_cm \- RDMA communication manager.
6 .B "#include <rdma/rdma_cma.h>"
8 Used to establish communication over RDMA transports.
10 The RDMA CM is a communication manager used to setup reliable, connected
11 and unreliable datagram data transfers. It provides an RDMA transport
14 communication must be over a specific RDMA device, and data transfers
17 The RDMA CM can control both the QP and communication management (connection setup /
18 teardown) portions of an RDMA API, or only the communication management
23 The RDMA CM can operate asynchronously or synchronously. The mode of
29 .SH "RDMA VERBS"
[all …]
|
| H A D | rdma_connect.3 | 6 .B "#include <rdma/rdma_cma.h>"
13 RDMA identifier.
40 The maximum number of outstanding RDMA read and atomic operations that the
42 This value must be less than or equal to the local RDMA device attribute
43 max_qp_rd_atom and remote RDMA device attribute max_qp_init_rd_atom. The
46 The maximum number of outstanding RDMA read and atomic operations that the
48 This value must be less than or equal to the local RDMA device attribute
49 max_qp_init_rd_atom and remote RDMA device attribute max_qp_rd_atom. The
58 times to retry send, RDMA, and atomic operations when timeouts occur.
87 Connections established over iWarp RDMA devices currently require that the
|
| H A D | rdma_getaddrinfo.3 | 6 .B "#include <rdma/rdma_cma.h>"
27 RDMA functional equivalent to getaddrinfo.
36 If node is provided, rdma_getaddrinfo will attempt to resolve the RDMA address,
39 If node is not given, rdma_getaddrinfo will attempt to resolve the RDMA addressing
59 Indicates the type of RDMA QP used for communication. Supported types are:
62 RDMA port space in use. Supported values are: RDMA_PS_UDP, RDMA_PS_TCP,
72 If provided, the address for the local RDMA device.
74 If provided, the address for the destination RDMA device.
84 Routing information for RDMA transports that require routing data as part
|
| H A D | rdma_reg_read.3 | 4 rdma_reg_read \- register data buffer(s) for remote RDMA read access.
6 .B "#include <rdma/rdma_verbs.h>"
21 Registers a memory buffer that will be accessed by a remote RDMA read
23 targeted in an RDMA read request, allowing the buffer to be
24 specified on the remote side of an RDMA connection as the remote_addr
31 target of an RDMA read operation on a queue pair associated with
|
| H A D | rdma_reg_write.3 | 4 rdma_reg_write \- register data buffer(s) for remote RDMA write access.
6 .B "#include <rdma/rdma_verbs.h>"
21 Registers a memory buffer that will be accessed by a remote RDMA write
23 targeted in an RDMA write request, allowing the buffer to be
24 specified on the remote side of an RDMA connection as the remote_addr
31 target of an RDMA write operation on a queue pair associated with
|
| H A D | rdma_create_id.3 | 6 .B "#include <rdma/rdma_cma.h>"
23 RDMA port space.
30 Rdma_cm_id's are conceptually equivalent to a socket for RDMA
31 communication. The difference is that RDMA communication requires
32 explicitly binding to a specified RDMA device before communication
46 Provides reliable, connection-oriented QP communication. Unlike TCP, the RDMA
|
| H A D | rdma_resolve_addr.3 | 6 .B "#include <rdma/rdma_cma.h>"
15 RDMA identifier.
24 to an RDMA address. If successful, the specified rdma_cm_id will
30 This call is used to map a given destination IP address to a usable RDMA
31 address. The IP to RDMA address mapping is done using the local routing
38 an RDMA device. This call is typically made from the active side of a
|
| H A D | mckey.1 | 4 mckey \- RDMA CM multicast setup and simple data transfer test.
16 Establishes a set of RDMA multicast communication paths between nodes
25 RDMA transport specific multicast address to join.
41 than the MTU of the underlying RDMA transport, or an error will occur.
45 The port space of the datagram communication. May be either the RDMA
56 Because this test maps RDMA resources to userspace, users must ensure
|
| H A D | udaddy.1 | 4 udaddy \- RDMA CM datagram setup and simple ping-pong test.
14 Establishes a set of unreliable RDMA datagram communication paths between two
21 communication. The used name or address must route over an RDMA device.
38 than the MTU of the underlying RDMA transport, or an error will occur.
46 The port space of the datagram communication. May be either the RDMA
52 Because this test maps RDMA resources to userspace, users must ensure
|
| H A D | rdma_get_devices.3 | 4 rdma_get_devices \- Get a list of RDMA devices currently available.
6 .B "#include <rdma/rdma_cma.h>"
14 Return a NULL-terminated array of opened RDMA devices. Callers can use
15 this routine to allocate resources on specific RDMA devices that will be
18 Returns an array of available RDMA devices, or NULL if the request
|
| H A D | ucmatose.1 | 4 ucmatose \- RDMA CM connection and simple ping-pong test.
16 Establishes a set of reliable RDMA connections between two nodes using the
22 connections. The used name or address must route over an RDMA device.
38 is the RDMA TCP port space. (Note that the RDMA port space may be separate
62 Because this test maps RDMA resources to userspace, users must ensure
|
| H A D | rsocket.7.in | 4 rsocket \- RDMA socket API
6 .B "#include <rdma/rsocket.h>"
8 RDMA socket API and protocol
10 Rsockets is a protocol over RDMA that supports a socket-level API
58 Riomap registers an application buffer with the RDMA hardware
95 specific to RDMA devices and protocols. These options are accessible
133 @CMAKE_INSTALL_FULL_SYSCONFDIR@/rdma/rsocket as shown:
153 echo 1000000 > @CMAKE_INSTALL_FULL_SYSCONFDIR@/rdma/rsocket/mem_default
|
| H A D | rdma_listen.3 | 6 .B "#include <rdma/rdma_cma.h>"
13 RDMA identifier.
27 address and the associated RDMA device. If the rdma_cm_id is bound
28 to an RDMA port number only, the listen will occur across all RDMA
|
| /freebsd/sys/ofed/include/rdma/ |
| H A D | rdma_cm.h | 41 #include <rdma/ib_addr.h>
42 #include <rdma/ib_sa.h>
46 * RDMA identifier and release all resources allocated with the device.
163 * rdma_create_id - Create an RDMA identifier.
169 * @ps: RDMA port space.
180 * rdma_destroy_id - Destroys an RDMA identifier.
182 * @id: RDMA identifier.
190 * rdma_bind_addr - Bind an RDMA identifier to a source address and
191 * associated RDMA device, if needed.
193 * @id: RDMA identifier.
[all …]
|
| /freebsd/contrib/ofed/librdmacm/ |
| H A D | rdma_cma.h | 48 * RDMA identifier and release all resources allocated with the device.
84 * RDMA CM.
235 * @ps: RDMA port space.
239 * Rdma_cm_id's are conceptually equivalent to a socket for RDMA
240 * communication. The difference is that RDMA communication requires
241 * explicitly binding to a specified RDMA device before communication
305 * rdma_bind_addr - Bind an RDMA identifier to a source address.
306 * @id: RDMA identifier.
311 * will also be bound to a local RDMA device.
324 * @id: RDMA identifier.
[all …]
|
| /freebsd/contrib/ofed/libibverbs/man/ |
| H A D | ibv_query_device.3 | 6 ibv_query_device \- query an RDMA device's attributes
36 …e; /* Maximum number of s/g per WR for SQ & RQ of QP for non RDMA Read operations */
37 int max_sge_rd; /* Maximum number of s/g per WR for RDMA Read opera…
42 int max_qp_rd_atom; /* Maximum number of RDMA Read & Atomic operations …
43 int max_ee_rd_atom; /* Maximum number of RDMA Read & Atomic operations …
44 int max_res_rd_atom; /* Maximum number of resources used for RDMA Read &…
45 int max_qp_init_rd_atom; /* Maximum depth per QP for initiation of RDMA Read…
46 int max_ee_init_rd_atom; /* Maximum depth per EEC for initiation of RDMA Rea…
|