[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] conduit + vchan

In the last weekly call I agreed to work on conduit + vchan.

Looking at the Lwt_unix conduit API


It seems to be using Lwt_io input/output channels. So my plan is to implement Lwt_io channels on top of the FLOW exposed by vchan. I've got a prototype of that here:

Does this general approach seem sensible? Since the conduit code is quite new and under heavy development I thought I'd better ask :-)

A side-benefit is that Lwt_unix apps which use vchan can decide to use either the Mirage FLOW interface or the Lwt_io interface.

It looks like the Mirage conduit interface is FLOW based, so I can expose the existing vchan implementation there.

Dave Scott
MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.