urbit/pkg/arvo/sys
Philip Monk 4e466214e3
arvo: compile hoon/arvo in separate roads
Adds +mure to run a trap in a separate road.  This should eventually be
just a hint.

Vega was running inside a mule, but since +load was called within vega,
the new kernel was all run within the same mule, so it didn't actually
get to reclaim the space after hoon compiled.

We verified this with printfs in u3m_fall.  On the test ship (from
mainnet) which had 800MB used, vega was taking interior free space from
950MB to 450 over the course of compiling hoon, then each vane would go
from about 450 to 350 and then back to 450 once it finished (which
proves they were correctly isolated).  With this change, after hoon
compiles the free space goes back up to 950MB.  This gives us a lot more
space to compile OTAs.

We had to slightly refactor the logic for doubly-recompiling hoon, since
+mure as written produces a ?(!! _trap), and you can't find faces in the
result of the trap.  We could bake mure, but that's rather awkward.  I
wonder if there's a way to fix this as a wet gate.
2020-06-12 20:51:23 -07:00
..
vane gall: properly handle empty outstanding ack queue 2020-06-05 17:05:22 -07:00
arvo.hoon arvo: compile hoon/arvo in separate roads 2020-06-12 20:51:23 -07:00
hoon.hoon arvo: compile hoon/arvo in separate roads 2020-06-12 20:51:23 -07:00
zuse.hoon ames: add |ames-wake 2020-05-28 10:28:31 -07:00