Re: [MirageOS-devel] MirageOS fortnightly call - Wednesday 1st at 4pm BST

[Hannes Mehnert <hannes@xxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA384

On 07/06/2015 17:06, Anil Madhavapeddy wrote:
> #### Networking stack
> 
> There were various issues around duplicate acks and TCP
> retransmission which were exposed due to the TLS stack integration.
> Many of these were just regressions or lurking issues due to Lwt
> mvars, and are now fixed.
> 
> To stop them from coming back, we now have tests that run per PR
> within Travis.  This uses vnetif to create virtual interfaces that
> directly short circuit the need for a real `tuntap` device, and so
> happily work great inside a container.  Coverage is patchy at the
> moment but is steadily improving (see 
> [mirage/mirage-tcpip#160](https://github.com/mirage/mirage-tcpip/issues/160)
>
> 
for coverage instructions).
> 
> ThomasG/L have put in [debug
> logging](https://github.com/mirage/mirage-tcpip/pull/152) so we now
> have full trace viewer capability.  When ThomasL looked at it,
> every connection ends with an exception being thrown, that noone
> had noticed before!  (The stack resolved a thread in RST processing
> and then looped again).  That issue is now fixed, but everyone is
> encouraged to use the browser profiler and find other lurking 
> issues.
> 
> Hannes has a TCP/IP test harness and will generate traces based on
> Peter Sewells [Netsem](http://www.cl.cam.ac.uk/~pes20/Netsem/).
> This has not been used much since 2005, but is being modernised for
> testing against Mirage TCP/IP.
> 
> Magnus and Mindy have written some iperf tests using the virtual
> vnetif interface.  Travis is timing out all the time due to very
> variable performance within their infrastructure, so its hard to
> figure out how much to test.  Anil suggested that we run them from
> cron against a repo like 
> [mirage/is-mirage-broken](https://github.com/mirage/is-mirage-broken).
>
>  The next feature that we are aiming for is to get IPv6 working
> with the stack. Nicolas Ojeda Bar has implemented everything
> needed, but the only thing blocking it is the configuration
> interface (which should be the easiest bit). Hannes, Justin and
> many others are keen on this...

btw, just online - some friends over at teclo do functional testing of
their TCP/IP stack:
http://www.snellman.net/blog/archive/2015-07-09-unit-testing-a-tcp-stack/

hannes

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCQAGBQJVnmfUAAoJELyJZYjffCjuv6YP/Rn8ymqtqLpMcu0/H7yk9dpO
LLYWN7LInZsR1ZcW6n/eR5qmv1uErojx2WrBNjBXaL5BypajaihjwASBOvHfCBip
F4FWjPuOxX1A05YPzNEedNHcKP/Nr02reKnGYvTq2PLhDlhRHNbt+F/ZDBHwFrNv
9Pm28JxseuXo7MsMGO2aB7qruN5oo1SZ4AQUq3+FtmZF5NpIqCI5q1VN6+sDjH8f
9jUol6E39TYhMnCeTb2itvDPdU1E0S6kb0IqEXigDlgdSjkjicPT0p9JXPyNh/wT
TODwTcA1vooONqUC+ZO5Mlid9L/UeG0GqP6fjd3/WaAYLCgVxNZTpkvaBEWs4fM5
m+a/LhpH0e1/mHAddx35B6qjQCgbc3nbHgHxUG+AVW2PhC3a3u7LEb4yXW1R84YL
93XdVXxvdj9tDXpaL3pi0MeHlwpp1tLx2AEHfbAdL8FLvmcigv8nYGQtMhbaY+wu
GyqxO1K+mgeC6BU/Yvvm75ht3KDTnhfvueqpiFEYe3dneXaN8oJbtHxZVv4FF+9V
r85zLJmOq8ZpTyW2RhZLcMpqUKD5ylCVxMq92gSd3iuJkAkQoS5pDpR3dAt0gDJv
e0rBvtzzoYaNnxsf96GeoW0xgD65ivb36FhhK59AnTpHl2N4tq6Wr/2aak/GEpwK
Bl5CMswyMxZfW3tbHo2g
=1mf3
-----END PGP SIGNATURE-----

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel