Short subjects: Realtime, Futexes, and ntfs3

Posted Aug 20, 2021 1:25 UTC (Fri) by NYKevin (subscriber, #129325)
In reply to: Short subjects: Realtime, Futexes, and ntfs3 by Cyberax
Parent article: Short subjects: Realtime, Futexes, and ntfs3

OK, but what do you use for the main event loop?

(Assume, for the sake of argument, that this is a non-GUI application such as a server, and so you're not just pumping window messages with GetMessage().)

Short subjects: Realtime, Futexes, and ntfs3

Posted Aug 20, 2021 3:45 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (2 responses)

> OK, but what do you use for the main event loop?
WFMO for the GUI apps :)

> (Assume, for the sake of argument, that this is a non-GUI application such as a server, and so you're not just pumping window messages with GetMessage().)

For server applications you should use either a good old thread-per-connection method or overlapped IO if you want asynchronous processing. WFMO was used in some of Ye Olde Servere Software to wait on large arrays of sockets, but that is roughly from the era when Linux only had select().

Short subjects: Realtime, Futexes, and ntfs3

Posted Aug 20, 2021 8:07 UTC (Fri) by njs (subscriber, #40338) [Link] (1 responses)

The problem is that there are objects that you can *only* wait on using WFMO -- so IOCP isn't enough, you need IOCP *and* WFMO, which is a terrific hassle.

Short subjects: Realtime, Futexes, and ntfs3

Posted Aug 20, 2021 17:09 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link]

Technically, you can use WFSO or WFMO _with_ IOCP to get notified about the signaled state.