undefined | Better HN

0 pointslayer810mo ago0 comments

The problem is when C calls expect to be on a particular thread. Either the main event thread, in a GUI context, or the same thread as some related previous call.

0 comments

ori_b10mo ago

The problem is that C expects to have enough stack to put stuff there, but green threads allocate small stacks to reduce (virtual) memory use.

layer8OP10mo ago

That’s not a problem when a dedicated thread pool is used as mentioned by GP. However they don’t solve the thread affinity issue.

ori_b10mo ago

That's the reason for the thread pool, and the resulting thread affinity issue.

layer8OP10mo ago

This seems to assume that the same green thread will always run on the same native thread, which I don’t think is universally the case.

2 more replies

j / k navigate · click thread line to collapse

0 comments

ori_b10mo ago

The problem is that C expects to have enough stack to put stuff there, but green threads allocate small stacks to reduce (virtual) memory use.

layer8OP10mo ago

That’s not a problem when a dedicated thread pool is used as mentioned by GP. However they don’t solve the thread affinity issue.

ori_b10mo ago

That's the reason for the thread pool, and the resulting thread affinity issue.

layer8OP10mo ago

This seems to assume that the same green thread will always run on the same native thread, which I don’t think is universally the case.

2 more replies

j / k navigate · click thread line to collapse