storiesManaging in a Complex Domain • Open discussion - need interactive communication, try crowd-sourcing or positive deviance - allow people to discuss solutions that are already working within the

thread for processing events: GUIs Client-Server applications Performing extensive processing on the event thread prevents other events from being handled.Why do we need to move work off the current thread current thread? We don’t just need to move the work, we need to prevent blocking on our event-handling threads. void event_handler(){ auto handle=spawn_background_task(); handle.wait(); // no benefit }Aside: Spawn a new thread for each event handlerHow do we move work off the current thread? Possible ways to move the work off the current thread: Spawn a new thread for each event handler Pass data to a dedicated

. . 34 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

. . 34 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

. . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

. . 36 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

. . 32 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

. . 31 2.3.3 C++ COM API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 2.3.4 Event queue processing . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3.5 Visual Basic and Visual the ptr.h file in the glue layer. 2.3.4 Event queue processing Both VirtualBox client programs and frontends should periodically perform processing of the main event queue, and do that on the application’s where an application using VirtualBox cannot directly control the main event loop and the main event queue is separated from the event queue of the programming librarly (for example in case of Qt on Unix

Intel Confidential Department or Event Name 1 © 2023 Intel Corporation and Jeffrey E. Erickson cppcon 2023 1cppcon 2023 Behavioral Modeling in HW/SW Co-design using C++ coroutines Jeffrey E Erickson Then: Address the problem Finally: Integrate with productionIntel Confidential Department or Event Name 4 © 2023 Intel Corporation and Jeffrey E. Erickson cppcon 2023 4 A Story and a Problem • You’re transactional/behavioral/functional definition to model the HW using SW elementsIntel Confidential Department or Event Name 5 © 2023 Intel Corporation and Jeffrey E. Erickson cppcon 2023 5 The Pace of RTL and C++ •

Application([ (r"/", MainHandler), ]) async def main(): app = make_app() app.listen(8888) await asyncio.Event().wait() if __name__ == "__main__": asyncio.run(main()) This example does not use any of Tornado’s ASYNCIO INTEGRATION Tornado is integrated with the standard library asyncio module and shares the same event loop (by default since Tornado 5.0). In general, libraries designed for use with asyncio can be mixed be very expensive. To minimize the cost of concurrent connections, Tornado uses a single-threaded event loop. This means that all appli- cation code should aim to be asynchronous and non-blocking because