Lines Matching +full:level +full:- +full:low
7 both low-level drivers that sit below the midlayer and upper level
13 With the following exceptions, a low-level driver implementation of
17 - create_ah
18 - modify_ah
19 - query_ah
20 - destroy_ah
21 - post_send
22 - post_recv
23 - poll_cq
24 - req_notify_cq
28 The corresponding functions exported to upper level protocol
31 - rdma_create_ah
32 - rdma_modify_ah
33 - rdma_query_ah
34 - rdma_destroy_ah
35 - ib_post_send
36 - ib_post_recv
37 - ib_req_notify_cq
43 - ib_dispatch_event
45 used by low-level drivers to dispatch asynchronous events through
49 ----------
51 All of the methods in struct ib_device exported by a low-level
52 driver must be fully reentrant. The low-level driver is required to
59 Because low-level drivers are reentrant, upper level protocol
67 ---------
69 A low-level driver must not perform a callback directly from the
71 allowed for a low-level driver to call a consumer's completion event
72 handler directly from its post_send method. Instead, the low-level
76 The low-level driver is responsible for ensuring that multiple
84 low-level driver ->
88 low-level driver ->
94 callbacks run is not defined. Depending on the low-level driver, it
96 Upper level protocol consumers may not sleep in a callback.
98 Hot-plug
99 --------
101 A low-level driver announces that a device is ready for use by
106 A low-level driver must call ib_register_device() and
111 An upper level protocol consumer may begin using an IB device as