runtime: move stack segment cache from M to P
It seems that the cache does not go away completely in 1.3,
so I think it's worth it to move the cache from M to P as other caches.
Large Go programs (especially the ones that use swig/cgo) can have hundreds of threads,
currently max cache size is 256K, so it can save some dozens of MBs.
Hello golang-codereviews@googlegroups.com (cc: iant@golang.org, khr@golang.org, rsc@golang.org), I'd like you to review this change to https://dvyukov%40google.com@code.google.com/p/go/
12 years, 4 months ago
(2014-02-25 13:54:49 UTC)
#1
This can crash, because exitsyscall splits stack w/o P. It would be nice to eventually ...
12 years, 4 months ago
(2014-02-27 17:08:20 UTC)
#3
This can crash, because exitsyscall splits stack w/o P. It would be nice to
eventually make it not split stack "outside of world" (w/o P). But let' not
rush.
R=close
Issue 10321043: code review 10321043: runtime: move stack segment cache from M to P
Created 13 years ago by dvyukov
Modified 12 years, 4 months ago
Reviewers: golang-codereviews, gobot, khr, bradfitz
Base URL:
Comments: 0