Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[new release] tcpip (4.1.0)
CHANGES:
A Lru.M.t allocates a Hashtbl.t of size = capacity (= 256 * 1024 in our case),
this leads to excessive ~2MB memory consumption for each Fragment cache,
reported by @xaki23 in serious memory issues since mirage-3.7 update mirage/qubes-mirage-firewall#93
SOCK_DGRAM which did not work)
reported by @justinc1 in Unix.EACCES error when running ping example mirage/mirage-tcpip#358, fixed in stack-unix: use a RAW socket for icmp (fixes #358) mirage/mirage-tcpip#424 by @hannesm
of (unit -> unit Lwt.t) (Start preparation for Lwt.async demanding unit Lwt.t mirage/mirage-tcpip#370 tcp: ignore result of xmit, continues #310, see #392 mirage/mirage-tcpip#425 @cfcs @hannesm, issue Should q.xmit return value be ignored? mirage/mirage-tcpip#392 @emillon)