Hi, On 05/30/2018 03:40 PM, Daniel J Williams wrote: > >> Can we use netdev struct to replace the index? Because the net device >> may have different parameters, not merely index. > > We have a solo5_net_info structure, which has mtu and mac address at the > moment and would likely need to grow at least to cover index. The > solo5_net_info call would also need to be updated to return info on the > particular device (although perhaps we should think about having some of that > in the start_info).
Including the NIC information in the start_info would simplify the Muen use case. This would also further codify the notion that the network configuration is static and does not change at runtime. >>>> The only risk is breaking the solo5 interface currently used by >>>> mirage and includeos. > > Are there examples of MirageOS unikernels that use two NICs on Xen or Unix? > That might be a starting point for understanding how the upper layers use > multiple devices. It sounds like there are already lots of examples of > IncludeOS using multiple NICs, maybe a pointer to some of the relevant code > will be helpful. An interesting scenario would be the Qubes Mirage Firewall, see [1]. I believe that unikernel uses multiple NICs. Cheers, Adrian [1] - https://github.com/talex5/qubes-mirage-firewall
