From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3136004f7805516af6f30ade7d125a01@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Wed, 13 Apr 2016 14:46:40 +0100
In-Reply-To: <6590113E-4E0B-4230-95B3-DCC51263FCEB@yahoo.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Go on Plan 9?
Topicbox-Message-UUID: 8d365e74-ead9-11e9-9d60-3106f5b1d025

> I didn=E2=80=99t realize that Go was so virtual memory hungry. I wonder=
 why stats didn=E2=80=99t show me a large peak of memory consumption befo=
re the go compiler died?

stats -m shows physical memory usage.  Every go program starts by allocat=
ing
a huge block of virtual space for its garbage-collected allocation arena.
A lot of that will normally remain unused, so no corresponding physical r=
am
need be allocated.

> Are these changes going to make it into the official kernel source? Any=
 reason why everyone, even non Go users, wouldn=E2=80=99t want the change=
s?

Depends what you mean by "official".  The rpi specific changes are all in
/n/sources/contrib/miller/9/bcm, and I will be sending patches for the po=
rtable
changes soon.  This is only for reference - it has been some time since a=
ny
patches were being applied on /n/sources/plan9.

> I didn=E2=80=99t realize that Go programs were so heavy weight. What do=
 embedded Go users have to do to make things work on other platforms like=
 Linux?

Depends what you mean by "embedded".  The VM allocation is probably less
significant for very small platforms than the size of the runtime library=
.

cpu% cat smallest.go
package main
func main() {
}
cpu% go build smallest.go
cpu% ls -l smallest
--rwxr-x--x M 3990 miller miller 614356 Apr 13 14:42 smallest
cpu% size smallest
466123t + 1792d + 87712b =3D 555627	smallest