Re: mirage + froc = self-scaling?

[Anil Madhavapeddy <anil@xxxxxxxxxx>]

Some background on FRP, and specifically the FROC self-adjusting library:
http://ambassadortothecomputers.blogspot.co.uk/2010/05/how-froc-works.html

The goal of this work is to encode the external dependencies of a Mirage 
unikernel explicitly, so that changes can ripple through the various 
computation units in a well-defined manner.  The tricky bit is that I/O threads 
('the outside world') need to be strongly separated from FROC ('the 
configuration space')

Consider the case of an ARP input packet, which needs to update a configuration 
variable (the ARP table), but is in the middle of doing some I/O.  However, we 
want to safely weave together static input (a static ARP configuration) with 
the dynamic inputs, which is where Froctol comes from.  There are many, many 
cases of such undefined behaviour in conventional operating systems: what 
happens to existing network sockets when a DHCP server rebinds an IP address on 
your machine?

Raphael, are your experiments with this from last summer available anywhere?  I 
couldn't spot them in your Github repo list.

-anil

On 28 Mar 2013, at 11:05, Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx> 
wrote:

> hi all;
> 
> after a chat with anil at asplos, i've begun playing around with using Froc 
> with Mirage (actually, in the first instance, using Froc with Lwt). FRP is 
> probably a good approach to try and encode notions of self-scaling that we've 
> talked about before -- so a Froc self-adjusting computation becomes the 
> overall framework within which Lwt threads execute to handle IO.
> 
> if anyone wants to take a look at what i've done so far, code is in 
> <https://github.com/mor1/froctal> (neat name, huh? :)  
> 
> this is very much work in progress, so suggestions for nice ways to integrate 
> Froc and Lwt gratefully received!
> 
> -- 
> Cheers,
> 
> R.
> 
> 
> 
> 
> This message and any attachment are intended solely for the addressee and may 
> contain confidential information. If you have received this message in error, 
> please send it back to me, and immediately delete it.   Please do not use, 
> copy or disclose the information contained in this message or in any 
> attachment.  Any views or opinions expressed by the author of this email do 
> not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.
>