there's a lot of prior art on timers - see http://www.cl.cam.ac.uk/research/dtg/lce-pub/public/kjm25/CUED_F-INFENG_TR487.pdf and references therein (e.g. druschel work on soft timers and the tiemr wheel stuff and use of calendar struct)
> On 12 November 2015 at 21:45, Hannes Mehnert <[email protected]> wrote: > > > > I'm eager to discuss it in further detail on this list (I'm pretty sure > > it is incomplete and partially wrong). > > > > https://gist.github.com/hannesm/17f478233508b42297d9 > > One thing I mentioned off-list, but would be interested in a wider > opinion on, is how best to handle timers, eg., for retransmission. > What seems to be the best thought I have on this so far is to turn the > appropriate responses from the pure core into a "transmission thread" > that will transmit and then retransmit packets according to whatever > schedule is mandated, and will be cancelled by suitable subsequent > response from the pure core. But other suggestions (or examples) > welcome! > > > Thanks to David and Mort for feedback on earlier drafts. Feedback > welcome, > > Thanks for writing it -- I've found it useful to refer to while > refactoring https://github.com/mor1/ocaml-tftp, which I believe is now > a lot cleaner than it was as a result :) > > -- > Richard Mortier > [email protected] > > _______________________________________________ > MirageOS-devel mailing list > [email protected] > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > _______________________________________________ MirageOS-devel mailing list [email protected] http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
