Re: Library unikernel or modularization of OSv kernel

[Dor Laor]

On Sat, May 5, 2018 at 9:48 AM, Waldek Kozaczuk 
wrote:

> What if there was a way early into the booting process to load specific
> features of OSv, that right now are linked in as part of kernel, as
> libraries? For example if we mounted ROFS as early and possible we could
> load other elements of the logic (configuration, ZFS, boost program options
> library, dhcp, etc) on demand and only as needed. Same way even some
> drivers could be loaded on demand later.
>
> Why would it be beneficial?
>

You can gain it all by preparing the right image ahead of time, so you'll
only have the features/setup you wish before boot.

What's good about your approach is that you can boot a generic image ahead
of time and only customize it once
you actually need to use it (when the first packet arrives) and thus save
the boot time


>
>- OSv kernel would be smaller and load even faster
>- OSv kernel can be modularized and therefore better tailored for
>specific hypervisor or application needs
>
> What do you think?
>
> Waldek
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Library unikernel or modularization of OSv kernel

[Geraldo Netto]

Hello Waldek/Friends!

That would be great Waldek!

Maybe some of those references might sound interesting/inspiring :)
http://www.lisha.ufsc.br/pub/Frohlich_2001.pdf
http://www.cse.unsw.edu.au/~ikuz/publications/jss.07.pdf
https://docs.sel4.systems/CAmkES/
http://univis.uni-erlangen.de/prg?search=projects=ciao;
director=preikschat=en=long

Probably you're already aware, but there are some really interesting papers
from TU Dresden/KIT/DATA61 CSIRO
But they are mainly focused on L4 family:
http://l4hq.org/
https://www.inf.tu-dresden.de/
http://os.itec.kit.edu (if I'm not mistaken, our friend "problame" from
issue  #952 studies here :P)



Kind Regards,

Geraldo Netto
Sapere Aude => Non dvcor, dvco
http://exdev.sf.net/

On 5 May 2018 at 13:48, Waldek Kozaczuk  wrote:

> What if there was a way early into the booting process to load specific
> features of OSv, that right now are linked in as part of kernel, as
> libraries? For example if we mounted ROFS as early and possible we could
> load other elements of the logic (configuration, ZFS, boost program options
> library, dhcp, etc) on demand and only as needed. Same way even some
> drivers could be loaded on demand later.
>
> Why would it be beneficial?
>
>- OSv kernel would be smaller and load even faster
>- OSv kernel can be modularized and therefore better tailored for
>specific hypervisor or application needs
>
> What do you think?
>
> Waldek
>
> --
> You received this message because you are subscribed to the Google Groups
> "OSv Development" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to osv-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Library unikernel or modularization of OSv kernel

[Waldek Kozaczuk]

What if there was a way early into the booting process to load specific 
features of OSv, that right now are linked in as part of kernel, as 
libraries? For example if we mounted ROFS as early and possible we could 
load other elements of the logic (configuration, ZFS, boost program options 
library, dhcp, etc) on demand and only as needed. Same way even some 
drivers could be loaded on demand later.

Why would it be beneficial?

   - OSv kernel would be smaller and load even faster
   - OSv kernel can be modularized and therefore better tailored for 
   specific hypervisor or application needs  
   
What do you think?

Waldek

-- 
You received this message because you are subscribed to the Google Groups "OSv 
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to osv-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.