Commit 653426f0 authored by Austin Clements's avatar Austin Clements

runtime: exit getfull barrier if there are partial workbufs

Currently, we only exit the getfull barrier if there is work on the
full list, even though the exit path will take work from either the
full or partial list. Change this to exit the barrier if there is work
on either the full or partial lists.

I believe it's currently safe to check only the full list, since
during mark termination there is no reason to put a workbuf on a
partial list. However, checking both is more robust.

Change-Id: Icf095b0945c7cad326a87ff2f1dc49b7699df373
Reviewed-on: https://go-review.googlesource.com/7840Reviewed-by: default avatarRick Hudson <rlh@golang.org>
parent 06de3f52
...@@ -419,7 +419,7 @@ func getfull(entry int) *workbuf { ...@@ -419,7 +419,7 @@ func getfull(entry int) *workbuf {
xadd(&work.nwait, +1) xadd(&work.nwait, +1)
for i := 0; ; i++ { for i := 0; ; i++ {
if work.full != 0 { if work.full != 0 || work.partial != 0 {
xadd(&work.nwait, -1) xadd(&work.nwait, -1)
b = (*workbuf)(lfstackpop(&work.full)) b = (*workbuf)(lfstackpop(&work.full))
if b == nil { if b == nil {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment