1dat_srq_resize(3DAT)Direct Access Transport Library Functiondsat_srq_resize(3DAT)
2
3
4
6 dat_srq_resize - modify the size of the shared receive queue
7
9 cc [ flag... ] file... -ldat [ library... ]
10 #include <dat/udat.h>
11
12 DAT_RETURN
13 dat_srq_resize (
14 IN DAT_SRQ_HANDLE srq_handle,
15 IN DAT_COUNT srq_max_recv_dto
16 )
17
18
20 srq_handle A handle for an instance of the SRQ.
21
22
23 srq_max_recv_dto The new maximum number of Recv DTOs that Shared
24 Receive Queue must hold.
25
26
28 The dat_srq_resize() function modifies the size of the queue of SRQ.
29
30
31 Resizing of Shared Receive Queue should not cause any incoming messages
32 on any of the EPs that use the SRQ to be lost. If the number of out‐
33 standing Recv buffers on the SRQ is larger then the requested
34 srq_max_recv_dto, the operation returns DAT_INVALID_STATE and do not
35 change SRQ. This includes not just the buffers on the SRQ but all out‐
36 standing Receive buffers that had been posted to the SRQ and whose com‐
37 pletions have not reaped yet. Thus, the outstanding buffers include the
38 buffers on SRQ, the buffers posted to SRQ at are at SRQ associated EPs,
39 and the buffers posted to SRQ for which completions have been generated
40 but not yet reaped by Consumer from recv_evds of the EPs that use the
41 SRQ.
42
43
44 If the requested srq_max_recv_dto is below the SRQ low watermark, the
45 operation returns DAT_INVALID_STATE and does not change SRQ.
46
48 DAT_SUCCESS The operation was successful.
49
50
51 DAT_INVALID_HANDLE The srq_handle argument is an invalid DAT
52 handle.
53
54
55 DAT_INVALID_PARAMETER The srq_max_recv_dto argument is invalid.
56
57
58 DAT_INSUFFICIENT_RESOURCES The operation failed due to resource lim‐
59 itations.
60
61
62 DAT_INVALID_STATE Invalid state. Either the number of
63 entries on the SRQ exceeds the requested
64 SRQ queue length or the requested SRQ
65 queue length is smaller than the SRQ low
66 watermark.
67
68
70 The dat_srq_resize() function is required not to lose any buffers.
71 Thus, it cannot shrink below the outstanding number of Recv buffers on
72 SRQ. There is no requirement to shrink the SRQ to return DAT_SUCCESS.
73
74
75 The quality of the implementation determines how closely to the Con‐
76 sumer-requested value the Provider shrinks the SRQ. For example, the
77 Provider can shrink the SRQ to the Consumer-requested value and if the
78 requested value is smaller than the outstanding buffers on SRQ, return
79 DAT_INVALID_STATE; or the Provider can shrink to some value larger than
80 that requested by the Consumer but below current SRQ size; or the
81 Provider does not change the SRQ size and still returns DAT_SUCCESS.
82
84 See attributes(5) for descriptions of the following attributes:
85
86
87
88
89 ┌─────────────────────────────┬─────────────────────────────┐
90 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
91 ├─────────────────────────────┼─────────────────────────────┤
92 │Interface Stability │Standard: uDAPL, 1.2 │
93 ├─────────────────────────────┼─────────────────────────────┤
94 │MT-Level │Unsafe │
95 └─────────────────────────────┴─────────────────────────────┘
96
98 dat_srq_create(3DAT), dat_srq_free(3DAT), dat_srq_post_recv(3DAT),
99 dat_srq_query(3DAT), dat_srq_set_lw(3DAT), libdat(3LIB), attributes(5)
100
101
102
103SunOS 5.11 16 Jul 2004 dat_srq_resize(3DAT)