Lines Matching refs:engine
73 only one asynchronous engine is being used then normally this call will only
100 by an engine immediately prior to calling ASYNC_pause_job() and not by end user
105 B<ENGINE *> for the engine. The I<custom_data> parameter can be any value, and
109 the B<ASYNC_WAIT_CTX> is freed, and gives the engine the opportunity to close
113 An example of typical usage might be an async capable engine. User code would
114 initiate cryptographic operations. The engine would initiate those operations
118 similar function on the wait file descriptor. The engine can signal to the user
120 "readable". Once resumed the engine should clear the wake signal on the wait
126 engine. This additional method can be used when the user thinks that a file
131 callback will be called to notify user code when an engine completes a
139 ASYNC_WAIT_CTX_set_status() allows an engine to set the current engine status.
146 The engine does not support the callback mechanism. This is the default value.
147 The engine must call ASYNC_WAIT_CTX_set_status() to set the status to some value
153 The engine has a fatal problem with this request. The user code should clean up
162 The engine has some problem which will be recovered soon, such as a buffer is
169 should not expect to receive a callback from the engine even if one has been
173 code would initiate cryptographic operations, and the engine code would dispatch
174 this operation to hardware, and if the dispatch is successful, then the engine
193 ASYNC_WAIT_CTX_get_status() returns the engine status.
