News for hackers. Stuff that matters.

A comment on Linux Namespaces and Go Don't Mix. Parent comment

Re:Linux Namespaces and Go Don't Mix by cyphar on Saturday June 03, 2017 @02:59AM (#14475361)
> I think it's unlikely Go will offer much more control over these internals (beyond GOMAXPROCS)

GOMAXPROCS is actually a lie. If you set it to 1, the runtime will still create threads.

[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by mappu on Saturday June 03, 2017 @05:28AM (#14475619)
> GOMAXPROCS is actually a lie. If you set it to 1, the runtime will still create threads.

It's not a lie. The variable is GOMAXPROCS, not GOMAXTHREADS. "procs" is specific jargon of the G:M:P scheduler design.

[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by cyphar on Saturday June 03, 2017 @07:33AM (#14475915)
Yeah, you're correct. Though it doesn't change that it's a deceptively named variable -- you have to read the runtime docs carefully to realise that it only refers to the number of threads concurrently executing Go code.
[ Parent | on HN ]