[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mirage 4.11.0 released! With built-in support for µTCP, and DNS/log/everything configuration via DHCP
- To: Hannes Mehnert <hannes@xxxxxxxxxxx>
- From: Anil Madhavapeddy <avsm2@xxxxxxxxxxxx>
- Date: Fri, 8 May 2026 13:57:40 +0100
- Authentication-results: eu.smtp.expurgate.cloud; dkim=pass header.s=20250721.smtp header.d=cam.ac.uk header.i="@cam.ac.uk" header.h="References:To:Cc:In-Reply-To:Date:Subject:Mime-Version:Content-Type:Message-Id:From"
- Cc: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Fri, 08 May 2026 12:58:03 +0000
- Feedback-id: i9ebc46d9:Fastmail
- List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
On May 8, 2026, at 1:49 PM, Hannes Mehnert <hannes@xxxxxxxxxxx> wrote:
µTCP (https://github.com/robur-coop/utcp) is a TCP stack developed from scratch based on the HOL4 model (https://www.cl.cam.ac.uk/~pes20/Netsem/). The stack is purely in OCaml and value-passing style (sans-IO, as pioneered by OCaml-TLS [David Kaloper Meršinjak]). Already now we have another backend for µTCP that doesn't rely on lwt - something very hard to do with the existing "old" TCP stack from https://github.com/mirage/mirage-tcpip (src/tcp).There is still ongoing work on µTCP, but we are also testing it since more than a year on some production systems on the Internet with good results. It is smaller, allocates less, and (hopefully) easier to maintain than the old TCP stack.
Great to see an alternative! How's the performance compared to mirage-tcpip? Congestion control was very complex to stabilise in mirage-tcpip back in the day.
best, Anil |
|
