| Quote: | “While L3 kernel can STILL run on MMU-less RAM-constrained MCUs, it provides responsiveness which is comparable to that of multi-stack kernels.” |
| Another Quote: | “multi-coring is essentially a special case of balancing shared-nothing nodes” |
| [→] |
TBH, I am a big fan of actor- and reactor-like programming patterns (also known as Finite State Machines. While you’re not strictly required to use reactors and might be able to get away without them – they DO provide several very substantial benefits.
(Re)Actors, page 1:
Bringing Architecture of Operating Systems to XXI Century – Part III. Basic Ideas
| Quote: | “everything in the system should be a Finite State Machine (FSM)” |
| Another Quote: | “‘OS’ is not understood as ‘OS kernel’, but rather is defined by the apps which can run on it” |
| [→] |
Bringing Architecture of Operating Systems to XXI Century – Part II. Desirable Improvements
| Quote: | “low-end versions of the new OS should be lean enough to run on a ~$1 MCU (these days ~=4K RAM, 32K ROM)” |
| Another Quote: | “last N minutes of the life of the production program before crashing, should be replayable on my development box.” |
| [→] |
Bringing Architecture of Operating Systems to XXI Century – Part I. Changes in IT Over Last 50 Years
| Quote: | “we’re using operating systems which were designed whopping 40-50 years from now” |
| Another Quote: | “Do not communicate by sharing memory; instead, share memory by communicating.” |
| [→] |
CAS (Re)Actor for Non-Blocking Multithreaded Primitives
| Quote: | in 2017, I started to feel that the Dark Ages of mutex-based thread sync were over |
| Another Quote: | Another issue which almost universally rears its ugly head when speaking about not-so-trivial uses of CAS is the so-called ABA problem. |
| [→] |
