Re: upcoming MirageOS meeting 2022-09-07

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

Hello again.

below are the notes. The next meeting is 2022-09-21 at 14:00 CEST in 
whereby.com/ocamllabs. I'm glad we took some decisions and started to 
merge some of the PRs.
# MirageOS meeting 2022-09-07

participants: lucas, hannes, pierre, reynir, christiano, talex5, taka, 
dinosaure
## qubes-mirage-firewall release (0.8)
- it is out, this time with mirage4 and PVH support
- fixes memory issues we had before (now using the footprint / dlmalloc 
from ocaml-solo5)
- still some memory issue when ocaml wants to allocate more memory than 
what's available 
(https://github.com/mirage/qubes-mirage-firewall/issues/143)
- unikernel is too slow (can't deal with bandwidth)
- also ongoing work: qrexec version 3 
https://github.com/mirage/mirage-qubes/pull/60
- some hardcoded DNS servers in there (see 
https://github.com/mirage/qubes-mirage-firewall/pull/142)
- remove UI code improves performance
- what is the packet rate? 1'000? 10'000? not clear, using iperf3
- old stats at https://github.com/mirage/qubes-mirage-firewall/pull/45, 
also https://github.com/mirage/qubes-mirage-firewall/issues/130
## mirage-flow "shutdown" https://github.com/mirage/mirage-flow/pull/48
- no comments

## mirage-flow "read" https://github.com/mirage/mirage-flow/issues/46
- maybe have both?
- eio: the reader has to provide the buffer by default, but the source 
can offer alternative optimisations.
- jane street has an annotation that a writer can only use the buffer 
until "read" is finished
-> propose a second function with the implementation thereof

## mirage-flow "write" (documentation update!)
for `write`: h2 reuses the buffer (so there's need for a copy); 
mirage-flow takes ownership of the buffer (thus deallocates it eventually)
## mirage-kv API enhancements (partial read, partial write, rename, 
size) https://github.com/mirage/mirage-kv/pull/28
- how hard is it to implement for irmin?
- let's merge and get some bounds for irmin etc.

## sunsetting Tcpip.Stack.V4 and Tcpip.Stack.V6 (in favour of 
Tcpip.Stack.V4V6) https://github.com/mirage/mirage/issues/1339
- agreed, let's merge

## tls-eio https://github.com/mirleft/ocaml-tls/pull/451
- CI is failing: add a "ocaml < 5" annotation to tls-async
- could get a review
- requires mirage-crypto-rng-eio (merge & release)



On 05/09/2022 15:00, Hannes Mehnert wrote:
> Hey,
>
> on this Wednesday, September 7th, starting at 14:00 CEST in 
> https://whereby.com/ocamllabs, we'll have a MirageOS meeting again.
> We'll take notes at https://pad.data.coop/kLbooYhzS-CUUd4vxp0qaA#
>
> The agenda so far has some API adjustments, and removing some deprecated 
> code -- feel free to add your other discussion points :)
> - mirage-flow "shutdown" https://github.com/mirage/mirage-flow/pull/48
> - mirage-flow "read" https://github.com/mirage/mirage-flow/issues/46
> - mirage-kv API enhancements (partial read, partial write, rename, size) 
> https://github.com/mirage/mirage-kv/pull/28 -- implementation status?
> - sunsetting Tcpip.Stack.V4 and Tcpip.Stack.V6 (in favour of 
> Tcpip.Stack.V4V6) https://github.com/mirage/mirage/issues/1339
>
> Best and see you on Wednesday!
>
> Hannes