[*] Formatting
[*] Revert-revert formatting
This commit is contained in:
parent
c0b0be52b1
commit
6fd844dae8
@ -9,9 +9,8 @@
|
||||
|
||||
/**
|
||||
It is not unusual for one to desire a unit-conversion constant when the developer understands
|
||||
[*] FPU isn't available
|
||||
[*] Can be done quickly without a framework
|
||||
[*] Using a framework to normalize to a base unit, apply a translation, and return the desired reuslt is considered overkill
|
||||
[*] An FPU isn't available
|
||||
[*] Using a framework to normalize to a base unit(?), apply a translation, and return the desired reuslt is considered overkill
|
||||
These functions are not to be converted into such a convoluted templated potentially-constexpr castable mess
|
||||
The intention is to keep these utility functions as simple as the dumb operations they implement
|
||||
*/
|
||||
|
17
README.md
17
README.md
@ -196,14 +196,15 @@ POSIX:
|
||||
|
||||
## Loop
|
||||
|
||||
The Aurora Runtime implements a loop concept similar to macos's RunLoop or BSD's kevent. On Mach platforms, kevent objects can
|
||||
be passed to loop sources. On BSD platforms, kevent objects can be used to synchronize against a wait any condition. On Linux,
|
||||
io_submit with epoll semantics can be used instead. NT, surpisingly where WaitForMultipleObjects is common, has the worst
|
||||
abstraction. Either way, all modern platforms provide a way to join file handles, an object from which you can derive any othe
|
||||
thread primitive from, semaphores, mutexes, network sockets, and asynchronous file transactions together. Aurora Runtime is
|
||||
implementing a loop source object and wait for any utility to solve this fiddly and complex abstraction. This should allow for
|
||||
non-bruteforced low thread count work groups to work on queues of ipcable objects across platforms with low synchronization
|
||||
overhead.
|
||||
The Aurora Runtime implements a kernel-scheduler optimized IO subsystem for managing Window, Network, File, IPC, and thread
|
||||
synchronization objects through loop the loop subsystem.
|
||||
|
||||
Loop sources are an interface defined by the loop subsystem for objects with a signalable state. Attached to a LoopQueue, the
|
||||
LoopQueue will provide a Wait-on related functions and subscription notifications of signal state change - allowing for optimized
|
||||
loop source removal or reinsert hints from the return values of the subscription interface. In addition, the ILoopSource interface
|
||||
permits arbitrary is-signaled-and-latch (TryLock) queries.
|
||||
|
||||
|
||||
|
||||
## Thread Primitives
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user