• Austin Clements's avatar
    runtime: flush write barrier buffer to create work · 9c634ea8
    Austin Clements authored
    Currently, if the gcWork runs out of work, we'll fall out of the GC
    worker, even though flushing the write barrier buffer could produce
    more work. While this is not a correctness issue, it can lead to
    premature mark 2 or mark termination.
    
    Fix this by flushing the write barrier buffer if the local gcWork runs
    out of work and then checking the local gcWork again.
    
    This reduces the number of premature mark terminations during all.bash
    by about a factor of 10.
    
    Updates #26903. This is preparation for eliminating mark 2.
    
    Change-Id: I48577220b90c86bfd28d498e8603bc379a8cd617
    Reviewed-on: https://go-review.googlesource.com/c/134315
    Run-TryBot: Austin Clements <austin@google.com>
    TryBot-Result: Gobot Gobot <gobot@golang.org>
    Reviewed-by: 's avatarRick Hudson <rlh@golang.org>
    9c634ea8
Name
Last commit
Last update
.github Loading commit data...
api Loading commit data...
doc Loading commit data...
lib/time Loading commit data...
misc Loading commit data...
src Loading commit data...
test Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
AUTHORS Loading commit data...
CONTRIBUTING.md Loading commit data...
CONTRIBUTORS Loading commit data...
LICENSE Loading commit data...
PATENTS Loading commit data...
README.md Loading commit data...
favicon.ico Loading commit data...
robots.txt Loading commit data...