source: doc/proposals/concurrency/notes/ @ cf966b5

Last change on this file since cf966b5 was db0fa7c, checked in by Thierry Delisle <tdelisle@…>, 7 years ago

Moved files and did some cleanup in the directories

  • Property mode set to 100644
File size: 486 bytes
1Internal scheduling notes.
3Internal scheduling requires a stack or queue to make sense.
4We also need a stack of "monitor contexts" to be able to restuore stuff.
6Multi scheduling try 1
7 - adding threads to many monitors and synching the monitors
8 - Too hard
10Multi scheduling try 2
11 - using a leader when in a group
12 - it's hard but doable to manage who is the leader and keep the current context
13 - basically __monitor_guard_t always saves an restore the leader and current context
Note: See TracBrowser for help on using the repository browser.