News for hackers. Stuff that matters.
Re:Multithreading Rust and Wasm by monocasa on Tuesday October 23, 2018 @03:31PM (#18286628)
At that point, the distinction between threads and processes gets really muddy even when you're not using wasm. clone(2) is just a superset of fork(2) that lets you decide whether to share memory or not (among other resources).
Re:Multithreading Rust and Wasm by namibj on Tuesday October 23, 2018 @09:29PM (#18288969)
I still think one could use a stackless clone(2) to get rid of the TLB flush when using threaded open(2). It would need to live without using the stack inside the clone however, and that's rather ugly to program.