3 ms·

I'd suspect NGPT was abandoned because they couldn't use growing stacks while staying compatible with C calling convention (but I wasn't able to find any confir

I'd suspect NGPT was abandoned because they couldn't use growing stacks while staying compatible with C calling convention (but I wasn't able to find any confirmation of this by googling). Go doesn't have this issue because it uses another calling convention.

pcwalton 9y ago
Stack growth is orthogonal to the M:N vs. 1:1 distinction. You can have large stacks with M:N or small stacks with 1:1.
- ngrilly 9y ago
  Are you saying we could use a 1:1 threading model with growing stacks (by growing stack I mean a stack that starts for example at 2 KB and is grown as needed)?
  - pcwalton 9y ago
    Sure. There are syscalls that allow a great deal of customization as to stack placement.
    - ngrilly 9y ago
      Thanks. I didn't know about that. What is the cost of context switching compared to userspace threading?