| /external/sdv/vsomeip/third_party/boost/asio/doc/overview/ |
| D | async.qbk | 10 The Boost.Asio library offers side-by-side support for synchronous and asynchronous
11 operations. The asynchronous support is based on the Proactor design pattern
25 [mdash] Asynchronous Operation
27 [:Defines an operation that is executed asynchronously, such as an asynchronous
30 [mdash] Asynchronous Operation Processor
32 [:Executes asynchronous operations and queues events on a completion event
34 services like `reactive_socket_service` are asynchronous operation processors.]
38 [:Buffers completion events until they are dequeued by an asynchronous event
43 [:Processes the result of an asynchronous operation. These are function
46 [mdash] Asynchronous Event Demultiplexer
[all …]
|
| D | handler_tracking.qbk | 10 To aid in debugging asynchronous programs, Boost.Asio provides support for handler
13 asynchronous operations and the relationships between their handlers.
17 asynchronous operations are chained together, or what the pending asynchronous
75 usually the case for any unfinished asynchronous operations when the
80 [The handler number `n` is about to create a new asynchronous operation with
82 information to help identify where in the program the asynchronous operation
87 [The handler number `n` created a new asynchronous operation with completion
88 handler number `m`. The `<description>` shows what asynchronous operation
96 asynchronous operations.]
100 [The implementation performed a system call as part of the asynchronous
[all …]
|
| D | implementation.qbk | 28 * An additional thread per `io_context` is used to emulate asynchronous host
48 * An additional thread per `io_context` is used to emulate asynchronous host
69 * An additional thread per `io_context` is used to emulate asynchronous host
91 * An additional thread per `io_context` is used to emulate asynchronous host
112 * An additional thread per `io_context` is used to emulate asynchronous host
133 * An additional thread per `io_context` is used to emulate asynchronous host
155 * An additional thread per `io_context` is used to emulate asynchronous host
177 * An additional thread per `io_context` is used to emulate asynchronous host
199 * An additional thread per `io_context` is used to emulate asynchronous host
220 * An additional thread per `io_context` is used to emulate asynchronous host
[all …]
|
| D | basics.qbk | 10 Boost.Asio may be used to perform both synchronous and asynchronous operations on I/O
64 When an asynchronous operation is used, a different sequence of events occurs.
78 The exact signature required depends on the asynchronous operation being
85 should start an asynchronous connect.
99 `io_context::run()` blocks while there are unfinished asynchronous operations,
101 asynchronous operation.
109 extending Boost.Asio to perform other types of asynchronous operations.
|
| /external/sdv/vsomeip/third_party/boost/asio/include/boost/asio/ |
| D | basic_deadline_timer.hpp | 42 * blocking or asynchronous wait for a timer to expire.
68 * Performing an asynchronous wait:
84 * // Start an asynchronous wait.
90 * Changing the expiry time of a timer while there are pending asynchronous
100 * // We managed to cancel the timer. Start new asynchronous wait.
119 * cancels any pending asynchronous waits, and returns the number of
120 * asynchronous waits that were cancelled. If it returns 0 then you were too
160 * dispatch handlers for any asynchronous operations performed on the timer.
174 * the timer will use, by default, to dispatch handlers for any asynchronous
191 * dispatch handlers for any asynchronous operations performed on the timer.
[all …]
|
| D | basic_waitable_timer.hpp | 53 * blocking or asynchronous wait for a timer to expire.
83 * Performing an asynchronous wait (C++11):
99 * // Start an asynchronous wait.
105 * Changing the expiry time of a timer while there are pending asynchronous
115 * // We managed to cancel the timer. Start new asynchronous wait.
134 * cancels any pending asynchronous waits, and returns the number of
135 * asynchronous waits that were cancelled. If it returns 0 then you were too
176 * dispatch handlers for any asynchronous operations performed on the timer.
190 * the timer will use, by default, to dispatch handlers for any asynchronous
207 * dispatch handlers for any asynchronous operations performed on the timer.
[all …]
|
| D | basic_signal_set.hpp | 38 * The basic_signal_set class provides the ability to perform an asynchronous
46 * Performing an asynchronous wait:
63 * // Start an asynchronous wait for one of the signals to occur.
116 * dispatch handlers for any asynchronous operations performed on the
130 * asynchronous operations performed on the signal set.
147 * dispatch handlers for any asynchronous operations performed on the
170 * asynchronous operations performed on the signal set.
196 * dispatch handlers for any asynchronous operations performed on the
225 * asynchronous operations performed on the signal set.
257 * dispatch handlers for any asynchronous operations performed on the
[all …]
|
| /external/cronet/net/base/ |
| D | file_stream.h | 32 // Uses |task_runner| for asynchronous operations.
38 // Uses |task_runner| for asynchronous operations.
57 // automatically closed when FileStream is destructed in an asynchronous
66 // It is invalid to request any asynchronous operations while there is an
67 // in-flight asynchronous operation.
77 // returned. It is invalid to request any asynchronous operations while there
78 // is an in-flight asynchronous operation.
94 // asynchronous read in progress. That will cancel the read and allow
97 // It is invalid to request any asynchronous operations while there is an
98 // in-flight asynchronous operation.
[all …]
|
| /external/sdv/vsomeip/third_party/boost/asio/doc/requirements/ |
| D | asynchronous_operations.qbk | 8 [section:asynchronous_operations Requirements on asynchronous operations]
16 [heading General asynchronous operation concepts]
19 asynchronous operation. A ['completion handler] is a function object that will
20 be invoked, at most once, with the result of the asynchronous operation.
22 The lifecycle of an asynchronous operation is comprised of the following events
25 [mdash] Event 1: The asynchronous operation is started by a call to the
28 [mdash] Phase 1: The asynchronous operation is now ['outstanding].
30 [mdash] Event 2: The externally observable side effects of the asynchronous
34 [mdash] Phase 2: The asynchronous operation is now ['completed].
37 asynchronous operation.
[all …]
|
| D | asynchronous_socket_operations.qbk | 8 [section:asynchronous_socket_operations Requirements on asynchronous socket operations]
10 In this library, ['asynchronous socket operations] are those member functions
13 For an object `s`, a program may initiate asynchronous socket operations such
14 that there are multiple simultaneously outstanding asynchronous operations.
16 When there are multiple outstanding asynchronous [link
28 When there are multiple outstanding asynchronous [link
34 When there are multiple outstanding asynchronous [link
|
| D | AsyncRandomAccessWriteDevice.qbk | 8 [section:AsyncRandomAccessWriteDevice Buffer-oriented asynchronous
11 In the table below, `a` denotes an asynchronous write stream object, `o`
17 [table Buffer-oriented asynchronous random-access write device requirements
28 Initiates an asynchronous operation to write one or more bytes of data to
31 boost_asio.reference.asynchronous_operations asynchronous operation]
46 [mdash] the handler for the asynchronous write operation is invoked,[br]
51 asynchronous write operation shall complete immediately and pass `0` as
|
| D | AsyncRandomAccessReadDevice.qbk | 8 [section:AsyncRandomAccessReadDevice Buffer-oriented asynchronous random-access
11 In the table below, `a` denotes an asynchronous random access read device
17 [table Buffer-oriented asynchronous random-access read device requirements
28 Initiates an asynchronous operation to read one or more bytes of data
31 boost_asio.reference.asynchronous_operations asynchronous operation]
45 [mdash] the handler for the asynchronous read operation is invoked,[br]
50 asynchronous read operation shall complete immediately and pass `0` as
|
| /external/tpm2-tss/doc/ |
| D | doxygen.dox | 5 Additionally there are asynchronous versions of each command.
7 Both the synchronous and asynchronous API are exposed through a single library: libtss2-esys.
119 * either as a one-call or in an asynchronous manner.
127 * either as a one-call or in an asynchronous manner.
135 * either as a one-call or in an asynchronous manner.
143 * either as a one-call or in an asynchronous manner.
151 * either as a one-call or in an asynchronous manner.
159 * either as a one-call or in an asynchronous manner.
165 * either as a one-call or in an asynchronous manner.
175 * either as a one-call or in an asynchronous manner.
[all …]
|
| /external/sdv/vsomeip/third_party/boost/asio/example/cpp11/timeouts/ |
| D | blocking_token_tcp_client.cpp | 31 // A custom completion token that makes asynchronous operations behave as
40 // The maximum time to wait for an asynchronous operation to complete.
51 // be used with asynchronous operations that have a completion signature of
58 // An asynchronous operation's initiating function automatically creates an
60 // then called on completion of the asynchronous operation.
92 // The return_type typedef determines the result type of the asynchronous
96 // The get() function is used to obtain the result of the asynchronous
108 // Block until the asynchronous operation has completed, or timed out. If in get()
109 // the pending asynchronous operation is a composed operation, the deadline in get()
114 // If the asynchronous operation completed successfully then the io_context in get()
[all …]
|
| /external/sdv/vsomeip/third_party/boost/asio/example/cpp03/timeouts/ |
| D | blocking_token_tcp_client.cpp | 31 // A custom completion token that makes asynchronous operations behave as
40 // The maximum time to wait for an asynchronous operation to complete.
51 // be used with asynchronous operations that have a completion signature of
58 // An asynchronous operation's initiating function automatically creates an
60 // then called on completion of the asynchronous operation.
92 // The return_type typedef determines the result type of the asynchronous
96 // The get() function is used to obtain the result of the asynchronous
108 // Block until the asynchronous operation has completed, or timed out. If in get()
109 // the pending asynchronous operation is a composed operation, the deadline in get()
114 // If the asynchronous operation completed successfully then the io_context in get()
[all …]
|
| /external/kotlinx.coroutines/kotlinx-coroutines-core/common/src/ |
| D | Timeout.kt | 29 …* **The timeout event is asynchronous with respect to the code running in the block** and may happ… in <lambda>()
33 …* [Asynchronous timeout and resources][https://kotlinlang.org/docs/reference/coroutines/cancellati… in <lambda>()
61 …* **The timeout event is asynchronous with respect to the code running in the block** and may happ…
65 …* [Asynchronous timeout and resources][https://kotlinlang.org/docs/reference/coroutines/cancellati…
88 …* **The timeout event is asynchronous with respect to the code running in the block** and may happ…
92 …* [Asynchronous timeout and resources][https://kotlinlang.org/docs/reference/coroutines/cancellati…
129 …* **The timeout event is asynchronous with respect to the code running in the block** and may happ…
133 …* [Asynchronous timeout and resources][https://kotlinlang.org/docs/reference/coroutines/cancellati…
|
| /external/tcpdump/ |
| D | gmpls.c | 81 { 5, "Asynchronous mapping of E4"},
82 { 6, "Asynchronous mapping of DS3/T3"},
83 { 7, "Asynchronous mapping of E3"},
86 { 10, "Asynchronous mapping of DS2/T2"},
89 { 13, "Asynchronous mapping of E1"},
92 { 16, "Asynchronous mapping of DS1/T1"},
98 { 22, "DS1 SF Asynchronous"},
99 { 23, "DS1 ESF Asynchronous"},
100 { 24, "DS3 M23 Asynchronous"},
101 { 25, "DS3 C-Bit Parity Asynchronous"},
|
| /external/sdv/vsomeip/third_party/boost/asio/example/cpp03/tutorial/ |
| D | timer_dox.txt | 69 This tutorial program demonstrates how to use asio's asynchronous callback
71 asynchronous wait on the timer.
78 Using asio's asynchronous functionality means having a callback
79 function that will be called when an asynchronous operation completes. In this
81 asynchronous wait finishes.
87 asynchronous wait. When calling this function we pass the <tt>print</tt>
98 the asynchronous wait completion will never be invoked.
101 still "work" to do. In this example, the work is the asynchronous wait on the
141 asynchronous wait. Obviously this means that the callback function will need
156 when there is no more "work" to do. By not starting a new asynchronous wait on
[all …]
|
| /external/openscreen/docs/ |
| D | trace_logging.md | 74 and asynchronous traces.
80 For asynchronous calls, the result must be set as part of the `TRACE_ASYNC_END`
108 ### Asynchronous Tracing
111 a new asynchronous function trace with name as provided. It will not end
115 as such, **this call should be used in the majority of asynchronous tracing
120 a new asynchronous function trace with name and full Trac ID Hierarchy as
128 (as described below). this function will initiate a new asynchronous
175 Asynchronous tracing with known Trace ID (recommended):
176 This approach allows for asynchronous tracing when the function being traced can
190 Asynchronous tracing with unknown Trace ID (not recommended):
[all …]
|
| /external/ms-tpm-20-ref/Samples/Nucleo-TPM/L4A6RG/ |
| D | Nucleo-L4A6RG.txt | 13 SYS Trace Asynchronous Sw SYS_JTMS-SWDIO PA13 (JTMS/SWDIO)
14 SYS Trace Asynchronous Sw SYS_JTCK-SWCLK PA14 (JTCK/SWCLK)
15 SYS Trace Asynchronous Sw SYS_JTDO-SWO PB3 (JTDO/TRACESWO)
17 USART2 Asynchronous USART2_RX PA3
18 USART2 Asynchronous USART2_TX PA2
|
| /external/sdv/vsomeip/third_party/boost/asio/include/boost/asio/windows/ |
| D | basic_object_handle.hpp | 44 * The windows::basic_object_handle class provides asynchronous and blocking
82 * dispatch handlers for any asynchronous operations performed on the
96 * asynchronous operations performed on the object handle.
114 * dispatch handlers for any asynchronous operations performed on the
137 * asynchronous operations performed on the object handle.
263 * This function is used to close the handle. Any asynchronous read or write
278 * This function is used to close the handle. Any asynchronous read or write
301 /// Cancel all asynchronous operations associated with the handle.
303 * This function causes all outstanding asynchronous read or write operations
316 /// Cancel all asynchronous operations associated with the handle.
[all …]
|
| /external/ms-tpm-20-ref/Samples/Nucleo-TPM/L476RG/ |
| D | Nucleo-L476RG.txt | 13 SYS Trace Asynchronous Sw SYS_JTMS-SWDIO PA13 (JTMS-SWDIO)
14 SYS Trace Asynchronous Sw SYS_JTCK-SWCLK PA14 (JTCK-SWCLK)
15 SYS Trace Asynchronous Sw SYS_JTDO-SWO PB3 (JTDO-TRACESWO)
17 USART2 Asynchronous USART2_RX PA3
18 USART2 Asynchronous USART2_TX PA2
|
| /external/sdv/vsomeip/third_party/boost/asio/include/boost/asio/detail/ |
| D | win_iocp_handle_service.hpp | 68 // The ID of the thread from which it is safe to cancel asynchronous
69 // operations. 0 means no asynchronous operations have been started yet.
70 // ~0 means asynchronous operations have been started from more than one
144 // Start an asynchronous write. The data being written must be valid for the
145 // lifetime of the asynchronous operation.
167 // Start an asynchronous write at a specified offset. The data being written
168 // must be valid for the lifetime of the asynchronous operation.
210 // Start an asynchronous read. The buffer for the data being received must be
211 // valid for the lifetime of the asynchronous operation.
234 // Start an asynchronous read at a specified offset. The buffer for the data
[all …]
|
| D | win_iocp_socket_service_base.hpp | 76 // The ID of the thread from which it is safe to cancel asynchronous
77 // operations. 0 means no asynchronous operations have been started yet.
78 // ~0 means asynchronous operations have been started from more than one
272 // Start an asynchronous send. The data being sent must be valid for the
273 // lifetime of the asynchronous operation.
298 // Start an asynchronous wait until data can be sent without blocking.
339 // Start an asynchronous receive. The buffer for the data being received
340 // must be valid for the lifetime of the asynchronous operation.
416 // Start an asynchronous receive. The buffer for the data being received
417 // must be valid for the lifetime of the asynchronous operation.
[all …]
|
| /external/sdv/vsomeip/third_party/boost/asio/include/boost/asio/posix/ |
| D | basic_descriptor.hpp | 85 * dispatch handlers for any asynchronous operations performed on the
99 * asynchronous operations performed on the descriptor.
117 * dispatch handlers for any asynchronous operations performed on the
141 * asynchronous operations performed on the descriptor.
270 * This function is used to close the descriptor. Any asynchronous read or
286 * This function is used to close the descriptor. Any asynchronous read or
316 * All outstanding asynchronous read or write operations will finish
325 /// Cancel all asynchronous operations associated with the descriptor.
327 * This function causes all outstanding asynchronous read or write operations
340 /// Cancel all asynchronous operations associated with the descriptor.
[all …]
|