1. 29 Mar, 2011 28 commits
  2. 28 Mar, 2011 11 commits
  3. 27 Mar, 2011 1 commit
    • Alexey Borzenkov's avatar
      runtime: fix darwin/amd64 thread VM footprint · 59a89268
      Alexey Borzenkov authored
      On darwin amd64 it was impossible to create more that ~132 threads. While
      investigating I noticed that go consumes almost 1TB of virtual memory per
      OS thread and the reason for such a small limit of OS thread was because
      process was running out of virtual memory. While looking at bsdthread_create
      I noticed that on amd64 it wasn't using PTHREAD_START_CUSTOM.
      If you look at http://fxr.watson.org/fxr/source/bsd/kern/pthread_synch.c?v=xnu-1228
      you will see that in that case darwin will use stack pointer as stack size,
      allocating huge amounts of memory for stack. This change fixes the issue
      and allows for creation of up to 2560 OS threads (which appears to be some
      Mac OS X limit) with relatively small virtual memory consumption.
      
      R=rsc
      CC=golang-dev
      https://golang.org/cl/4289075
      59a89268