On 07/12/2016 05:00 PM, Hannes Mehnert wrote:
On 17/06/2016 10:26, Mindy wrote:
* Arp could be refactored not to use wall-clock time for judging whether
to expire entries, but a proper dynamic implementation still needs some
dependency on the current TIME signature, I think.
What I meant in this thread with external timer events I now wrote down
-- https://hannes.nqsb.io/Posts/ARP https://github.com/hannesm/arp
Unfortunately not easy to drop in as a replacement since mirage - the
tool - has pretty much hardcoded tcpip.arpv4 and Arpv4 as a module name.
This issue, generally, is something I've been mulling over for a while.
When I'm building unikernels that use some custom implementation I just
do an end-run around the mirage front-end tool, but it really feels like
something that should be supported.
Upside: found a bug in mirage-tcpip
(https://github.com/mirage/mirage-tcpip/issues/225 via Martin's
unikernel-runner)
Downside: V1.ARP does not have the right semantics... how useful is an
ARP handler which has no IPv4 address?
Upside: that's fixable.
-Mindy
_______________________________________________
MirageOS-devel mailing list
[email protected]
https://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
