1. 23 Jan, 2014 3 commits
    • Russ Cox's avatar
      lib/codereview: add LGTM= line to commit messages · 672ab629
      Russ Cox authored
      The R= is populated by Rietveld, so it's basically
      anyone who replied to the CL. The LGTM= is meant
      to record who actually signed off on the CL.
      
      LGTM=r
      R=r
      CC=golang-codereviews
      https://golang.org/cl/55390043
      672ab629
    • Dmitriy Vyukov's avatar
      undo CL 45770044 / d795425bfa18 · 8371b014
      Dmitriy Vyukov authored
      Breaks darwin and freebsd.
      
      ««« original CL description
      runtime: increase page size to 8K
      Tcmalloc uses 8K, 32K and 64K pages, and in custom setups 256K pages.
      Only Chromium uses 4K pages today (in "slow but small" configuration).
      The general tendency is to increase page size, because it reduces
      metadata size and DTLB pressure.
      This change reduces GC pause by ~10% and slightly improves other metrics.
      
      json-1
      allocated                 8037492      8038689      +0.01%
      allocs                     105762       105573      -0.18%
      cputime                 158400000    155800000      -1.64%
      gc-pause-one              4412234      4135702      -6.27%
      gc-pause-total            2647340      2398707      -9.39%
      rss                      54923264     54525952      -0.72%
      sys-gc                    3952624      3928048      -0.62%
      sys-heap                 46399488     46006272      -0.85%
      sys-other                 5597504      5290304      -5.49%
      sys-stack                  393216       393216      +0.00%
      sys-total                56342832     55617840      -1.29%
      time                    158478890    156046916      -1.53%
      virtual-mem             256548864    256593920      +0.02%
      
      garbage-1
      allocated                 2991113      2986259      -0.16%
      allocs                      62844        62652      -0.31%
      cputime                  16330000     15860000      -2.88%
      gc-pause-one            789108229    725555211      -8.05%
      gc-pause-total            3945541      3627776      -8.05%
      rss                    1143660544   1132253184      -1.00%
      sys-gc                   65609600     65806208      +0.30%
      sys-heap               1032388608   1035599872      +0.31%
      sys-other                37501632     22777664     -39.26%
      sys-stack                 8650752      8781824      +1.52%
      sys-total              1144150592   1132965568      -0.98%
      time                     16364602     15891994      -2.89%
      virtual-mem            1327296512   1313746944      -1.02%
      
      R=golang-codereviews, dave, khr, rsc, khr
      CC=golang-codereviews
      https://golang.org/cl/45770044
      »»»
      
      R=golang-codereviews
      CC=golang-codereviews
      https://golang.org/cl/56060043
      8371b014
    • Dmitriy Vyukov's avatar
      runtime: increase page size to 8K · 6d603af6
      Dmitriy Vyukov authored
      Tcmalloc uses 8K, 32K and 64K pages, and in custom setups 256K pages.
      Only Chromium uses 4K pages today (in "slow but small" configuration).
      The general tendency is to increase page size, because it reduces
      metadata size and DTLB pressure.
      This change reduces GC pause by ~10% and slightly improves other metrics.
      
      json-1
      allocated                 8037492      8038689      +0.01%
      allocs                     105762       105573      -0.18%
      cputime                 158400000    155800000      -1.64%
      gc-pause-one              4412234      4135702      -6.27%
      gc-pause-total            2647340      2398707      -9.39%
      rss                      54923264     54525952      -0.72%
      sys-gc                    3952624      3928048      -0.62%
      sys-heap                 46399488     46006272      -0.85%
      sys-other                 5597504      5290304      -5.49%
      sys-stack                  393216       393216      +0.00%
      sys-total                56342832     55617840      -1.29%
      time                    158478890    156046916      -1.53%
      virtual-mem             256548864    256593920      +0.02%
      
      garbage-1
      allocated                 2991113      2986259      -0.16%
      allocs                      62844        62652      -0.31%
      cputime                  16330000     15860000      -2.88%
      gc-pause-one            789108229    725555211      -8.05%
      gc-pause-total            3945541      3627776      -8.05%
      rss                    1143660544   1132253184      -1.00%
      sys-gc                   65609600     65806208      +0.30%
      sys-heap               1032388608   1035599872      +0.31%
      sys-other                37501632     22777664     -39.26%
      sys-stack                 8650752      8781824      +1.52%
      sys-total              1144150592   1132965568      -0.98%
      time                     16364602     15891994      -2.89%
      virtual-mem            1327296512   1313746944      -1.02%
      
      R=golang-codereviews, dave, khr, rsc, khr
      CC=golang-codereviews
      https://golang.org/cl/45770044
      6d603af6
  2. 22 Jan, 2014 26 commits
  3. 21 Jan, 2014 11 commits
    • Brad Fitzpatrick's avatar
      syscall: add Flock_t.Lock method · 5d3033c5
      Brad Fitzpatrick authored
      Fixes #7059
      
      R=golang-codereviews, iant, mikioh.mikioh
      CC=golang-codereviews
      https://golang.org/cl/53470043
      5d3033c5
    • Keith Randall's avatar
      runtime: if "panic during panic"'s stacktrace fails, don't recurse. · c8c18614
      Keith Randall authored
      R=golang-codereviews, iant, khr, dvyukov
      CC=golang-codereviews
      https://golang.org/cl/54160043
      c8c18614
    • Russ Cox's avatar
      cmd/link: add testdata/pclntab.6 (fix build) · 2a2a3baa
      Russ Cox authored
      Sorry, "hg status" hides .6 files by default.
      We should probably fix that.
      
      TBR=iant
      CC=golang-codereviews
      https://golang.org/cl/55290043
      2a2a3baa
    • Ian Lance Taylor's avatar
      cmd/gc: document -pack flag · bec1a3e2
      Ian Lance Taylor authored
      R=golang-codereviews, r
      CC=golang-codereviews
      https://golang.org/cl/55140044
      bec1a3e2
    • Russ Cox's avatar
      cmd/link: pclntab generation · a453f28c
      Russ Cox authored
      R=iant
      CC=golang-codereviews
      https://golang.org/cl/53820043
      a453f28c
    • Russ Cox's avatar
      cmd/gc: fix build · 0dd26f27
      Russ Cox authored
      The AKILL stuff is not ready yet and
      was not meant to be in the last CL.
      
      R=iant
      CC=golang-codereviews
      https://golang.org/cl/55170043
      0dd26f27
    • Russ Cox's avatar
      cmd/gc: do not follow uintptr passed as function argument · eb592d82
      Russ Cox authored
      The escape analysis works by tracing assignment paths from
      variables that start with pointer type, or addresses of variables
      (addresses are always pointers).  It does allow non-pointers
      in the path, so that in this code it sees x's value escape into y:
      
              var x *[10]int
              y := (*int)(unsafe.Pointer(uintptr(unsafe.Pointer(x))+32))
      
      It must allow uintptr in order to see through this kind of
      "pointer arithmetic".
      
      It also traces such values if they end up as uintptrs passed to
      functions. This used to be important because packages like
      encoding/gob passed around uintptrs holding real pointers.
      
      The introduction of precise collection of stacks has forced
      code to be more honest about which declared stack variables
      hold pointers and which do not. In particular, the garbage
      collector no longer sees pointers stored in uintptr variables.
      Because of this, packages like encoding/gob have been fixed.
      
      There is not much point in the escape analysis accepting
      uintptrs as holding pointers at call boundaries if the garbage
      collector does not.
      
      Excluding uintptr-valued arguments brings the escape
      analysis in line with the garbage collector and has the
      useful side effect of making arguments to syscall.Syscall
      not appear to escape.
      
      That is, this CL should yield the same benefits as
      CL 45930043 (rolled back in CL 53870043), but it does
      so by making uintptrs less special, not more.
      
      R=golang-codereviews, iant
      CC=golang-codereviews
      https://golang.org/cl/53940043
      eb592d82
    • Russ Cox's avatar
      cmd/gc: fix crash in -live debugging output · 8027660a
      Russ Cox authored
      R=golang-codereviews, iant
      CC=golang-codereviews
      https://golang.org/cl/53930043
      8027660a
    • Ian Lance Taylor's avatar
      cmd/ld: support archives larger than 2G · cdc55655
      Ian Lance Taylor authored
      R=golang-codereviews, gobot, rsc
      CC=golang-codereviews
      https://golang.org/cl/53950043
      cdc55655
    • Ian Lance Taylor's avatar
      liblink: check for symgrow size too large · 6111dc4e
      Ian Lance Taylor authored
      Many calls to symgrow pass a vlong value.  Change the function
      to not implicitly truncate, and to instead give an error if
      the value is too large.
      
      R=golang-codereviews, gobot, rsc
      CC=golang-codereviews
      https://golang.org/cl/54010043
      6111dc4e
    • Dmitriy Vyukov's avatar
      runtime: do not collect GC roots explicitly · cb133c66
      Dmitriy Vyukov authored
      Currently we collect (add) all roots into a global array in a single-threaded GC phase.
      This hinders parallelism.
      With this change we just kick off parallel for for number_of_goroutines+5 iterations.
      Then parallel for callback decides whether it needs to scan stack of a goroutine
      scan data segment, scan finalizers, etc. This eliminates the single-threaded phase entirely.
      This requires to store all goroutines in an array instead of a linked list
      (to allow direct indexing).
      This CL also removes DebugScan functionality. It is broken because it uses
      unbounded stack, so it can not run on g0. When it was working, I've found
      it helpless for debugging issues because the two algorithms are too different now.
      This change would require updating the DebugScan, so it's simpler to just delete it.
      
      With 8 threads this change reduces GC pause by ~6%, while keeping cputime roughly the same.
      
      garbage-8
      allocated                 2987886      2989221      +0.04%
      allocs                      62885        62887      +0.00%
      cputime                  21286000     21272000      -0.07%
      gc-pause-one             26633247     24885421      -6.56%
      gc-pause-total             873570       811264      -7.13%
      rss                     242089984    242515968      +0.18%
      sys-gc                   13934336     13869056      -0.47%
      sys-heap                205062144    205062144      +0.00%
      sys-other                12628288     12628288      +0.00%
      sys-stack                11534336     11927552      +3.41%
      sys-total               243159104    243487040      +0.13%
      time                      2809477      2740795      -2.44%
      
      R=golang-codereviews, rsc
      CC=cshapiro, golang-codereviews, khr
      https://golang.org/cl/46860043
      cb133c66