Lines Matching full:request
85 once the request has completed.
90 once the request has completed.
112 allocates a new request that inherits request inputs such as request buffers
115 request.
116 However, the new request is associated with the
121 must not be a completed request.
123 Once a request has been initialized,
125 request-specific parameters.
134 request's session.
135 If there are errors in the request's fields, these functions may return an
137 If errors are encountered while servicing the request, they will instead
138 be reported to the request's callback function
143 Note that a request's callback function may be invoked before
147 Once a request has signaled completion by invoking its callback function,
153 Cryptographic operations include several fields to describe the request.
154 .Ss Request Buffers
218 .Ss Request Regions
219 Each request describes one or more regions in the data buffers.
270 .Ss Request Operations
300 complete the request successfully.
302 fail the request with
319 fail the request with
322 .Ss Request AAD
331 .Ss Request ESN
349 .Ss Request IV and/or Nonce
367 .Ss Request and Callback Scheduling
375 functions can be used to request different dispatch scheduling policies.
378 synchronously passes the request to the driver.
379 The driver itself may process the request synchronously or asynchronously
383 dispatches the request asynchronously.
384 If the driver is inherently synchronous, the request is queued to a taskqueue
406 This allows hardware drivers to optimize the scheduling of request processing
409 each request, specifying
411 with each request except for the last.
418 Callback function scheduling is simpler than request scheduling.
438 the callback is invoked synchronously if the request was processed by a
439 software driver or asynchronously if the request was processed by a
442 If a request was scheduled to the taskqueue with
450 .Ss Other Request Fields
457 This is set when the request is created by
464 Either zero on success, or an error if a request fails.
465 Set by drivers prior to completing a request via
481 Pointer to a request-specific encryption key.
483 the request uses the session encryption key.
485 Pointer to a request-specific authentication key.
487 the request uses the session authentication key.
491 information about a request to be used in the callback.
499 It should also arrange for the request to be freed via
505 If a compression request increases the size of the payload,
506 then the data buffer is unmodified, the request completes successfully,
515 returns an error if the request contained invalid fields,
516 or zero if the request was valid.
518 returns a pointer to a new request structure on success,
535 Not all drivers properly handle mixing session and per-request keys
538 the session parameters or always use per-request keys.