[rust-dev] Idea: Memcpyed stacks for green tasks

comex comexk at gmail.com
Sat Jan 25 18:23:34 PST 2014

To me, issues such as large memcpys/system calls on context switches,
having tasks not be able to compute concurrently with random other
tasks, possibly having to autobox everything, etc. sound like they
would spawn equal or greater complexity and performance loss than just
using split stacks.

If you really wanted to avoid wasting memory, couldn't you allow new
tasks to steal memory below the stack pointer of swapped-out tasks,
changing that task's stack bottom pointer in the process?

More information about the Rust-dev mailing list