]> Cypherpunks repositories - gostls13.git/commitdiff
runtime: remove GoSched/GoStart trace events around GC
authorAustin Clements <austin@google.com>
Thu, 9 Apr 2015 14:17:06 +0000 (10:17 -0400)
committerAustin Clements <austin@google.com>
Fri, 10 Apr 2015 18:21:52 +0000 (18:21 +0000)
These were appropriate for STW GC, since it interrupted the allocating
Goroutine, but don't apply to concurrent GC, which runs on its own
Goroutine. Forced GC is still STW, but it makes sense to attribute the
GC to the goroutine that called runtime.GC().

Change-Id: If12418ca66dc7e53b8b16025af4e03adb5d9577e
Reviewed-on: https://go-review.googlesource.com/8715
Reviewed-by: Dmitry Vyukov <dvyukov@google.com>
Reviewed-by: Rick Hudson <rlh@golang.org>
src/runtime/mgc.go

index e8cf95e9071d0bb8dc5301f02f584a05d5221a0c..8ed8c573627c5e49631e8a112499fc21c279d87d 100644 (file)
@@ -324,7 +324,6 @@ func gc(mode int) {
        }
 
        if trace.enabled {
-               traceGoSched()
                traceGCStart()
        }
 
@@ -459,7 +458,6 @@ func gc(mode int) {
 
        if trace.enabled {
                traceGCDone()
-               traceGoStart()
        }
 
        // all done