Lines Matching full:requests
77 Requests can either be allocated dynamically or use caller-supplied
79 Dynamically allocated requests should be allocated by either
86 Requests using caller-supplied storage should be initialized by
133 functions pass one or more crypto requests to the driver attached to the
155 Requests can either specify a single data buffer that is modified in place
169 mode requests.
171 All requests must have a valid
197 for requests that use separate input and output buffers:
222 The length of some regions is the same for all requests belonging to
226 All requests must define a payload region.
229 For requests with separate input and output data buffers,
235 requests that verify an existing digest.
236 For requests that compute a digest,
266 Requests are permitted to operate on only a subset of the data buffer.
268 requests from IPsec operate on network packets that include headers not
271 All requests must specify the type of operation to perform in
275 Compression requests support the following operations:
283 Cipher requests support the following operations:
291 Digest requests support the following operations:
306 AEAD and Encrypt-then-Authenticate requests support the following
323 AEAD and Encrypt-then-Authenticate requests may optionally include
332 IPsec requests may optionally include Extended Sequence Numbers (ESN).
364 Requests that store part, but not all, of the IV in the data buffer should
369 of requests to drivers along with the processing of driver callbacks.
386 This can increase througput by allowing requests from a single producer to be
389 Worker threads dequeue requests and pass them to the driver asynchronously.
396 flag indicates that completion callbacks for requests must be called in the
397 same order as requests were dispatched.
404 allows the caller to collect a batch of requests and submit them to the driver
502 Used with compression and decompression requests to describe the updated