• Austin Clements's avatar
    runtime: don't use cached wbuf in markroot · 77fcf36a
    Austin Clements authored
    Currently markroot fetches the wbuf to fill from the per-M wbuf
    cache. The wbuf cache is primarily meant for the write barrier because
    it produces very little work on each call. There's little point to
    using the cache in mark root, since each call to markroot is likely to
    produce a large amount of work (so the slight win on getting it from
    the cache instead of from the central wbuf lists doesn't matter), and
    markroot does not dispose the wbuf back to the cache (so most markroot
    calls won't get anything from the wbuf cache anyway).
    
    Instead, just get the wbuf from the central wbuf lists like other work
    producers. This will simplify later changes.
    
    Change-Id: I07a18a4335a41e266a6d70aa3a0911a40babce23
    Reviewed-on: https://go-review.googlesource.com/7732Reviewed-by: default avatarRick Hudson <rlh@golang.org>
    77fcf36a
mgcmark.go 19.1 KB