note that the heap goes one direction during the lifetime of a process, but gets torn down upon process exit (corresponding to levels of the process call graph). meanwhile, the....parallel process branching corresponds to the....perpendicular axis of the process call graph????
and the "process call graph" is only ever a tree of living processes at any one time, but:
- process exit closes a recursive subtree (along with current heap/break) at once (hence why init must always be live)
- the process start and exit marks always have a strictly positive delta of clock cycles????
and the "persistent block layer" (aka "filesystem") can also be mapped into process memory—but because it persists, it exists automatically across all processes, with the kernel/fs acting as the block layer MMU through file descriptors!!!! but filesystem paths and the VFS are not real at all—AND THIS IS WHY PATHS (windows) AND VFS NODE TYPES ARE UNSTABLE ACROSS OPERATING SYSTEMS!!!
oh and multicore is a parallel (fixed-width) execution of <= k monotonic processor clocks at once, and the scheduler is the MMU for task execution (IMPLYING RECURSIVE SCHEDULING IS NOT ONLY PLAUSIBLE BUT OBVIOUS!!!!). so each process is scheduled on <= 1 core at a time, with each such strand organized in strictly monotonic chron order across all cores, constituting a series of "on(core)" (vertex-colored) and "off" regions in the global (unmeasurable) "wall-clock" monotonic chronic arrangement.
in recording this 3-D (2-D in-process, 3rd is core index) discrete plot of the in-process 2-axis states, this time-series instruction-pointer plot can be used to infer ("parse") the runtime function call stack & branch–jump history retroactively for a given process execution.
but what's this about assigning vertex-color-per-core? vertex coloration per core just means only one core can iterate the task's literal core-unaware turing machine at once, and the (totally-ordered and directed) edges connect the contributions from each core. when an edge makes a task cross cores, that requires the CPU to flush per-core caches for any addresses in that process's virtual mem.