3 ms·
I suppose the trick, then, would be to take a bare system call and somehow automatically promote it to a process in the operating system? You could do this for
by jimbokun 16y ago
I suppose the trick, then, would be to take a bare system call and somehow automatically promote it to a process in the operating system?
You could do this for a given function signature, perhaps. But it's not clear how it would work in the general case. Is there some universal function signature that makes sense for any kind of API, that makes sense both for pipes and for the semantics of the specific program?
Interesting to think about, though.
- jacquesm 16y agoYou're on the way to re-inventing Erlang I think ;) That would be one way to do it, but system calls are generally assumed to be atomic, promoting them to process status would be quite tricky. Multi-threaded kernels effectively do some of this by allowing you to execute multiple system calls in parallel. The typical way in which an 'image' based system works is that all your persistence (including compiled code) continues to reside in the image, over time you get the same kind of build-up that you typically see in file systems, only there there is no difference between 'programs' and 'subroutines'.