25 ms·

https://dl.acm.org/doi/pdf/10.1145/3709714 https://dl.acm.org/doi/pdf/10.1145/3709714 sounds pretty similar motivation-wise to this. would be interested if lin

by seb711 1y ago

https://dl.acm.org/doi/pdf/10.1145/3709714 https://dl.acm.org/doi/pdf/10.1145/3709714 sounds pretty similar motivation-wise to this. would be interested if linux as a host system is still needed. and if not: how is heterogenous hardware supported without virtualization?

dataware-admin 1y ago
We don't think it is needed. Currently, the only thing which is stopping it from running on bare-metal no hypervisor are some drivers for virtual devices (eg. virtio net driver). Challenge is, ofc, supporting wide range of hardware options, but we don't intend to. We plan to support only modern x86_64 CPUs (arm is on the roadmap) and a select few NICs. Current implementation is written to be hosted on public cloud, so we implement what is needed for that, but in the future we intend to allow self hosted version, but only on selected server hardware. Now, if we have "big" server with like 256 cpus, etc. we can still split it many smaller "vms". Since the only code that runs with Hardware Manager is code we write, we can just add config options which pin execution to resources, eg. ram, we can just allow it to use from 4gb-8gb phys addr. Shared hardware like NIC is a bit trickier, but we do have some tricks up our sleeve which allow sharing.
- seb711 1y ago
  > which is stopping it from running on bare-metal no hypervisor are some drivers for virtual devices (eg. virtio net driver). why would you need to support virtual devices, if you are not in a virtualized environment?
  - dataware-admin 1y ago
    Yea poor phrasing in that sentance. All code we have can already run on bare-metal except some drivers, since most are only for virtualized devices. Hopefuly that clears what we wanted to say. If we implement eg nic driver for physical device then we can run bare-metal no host at all.
    - seb711 1y ago
      Sounds great! This is the future!
      - dataware-admin 1y ago
        Glad you like it Btw, we fixed some whitelist issues and if you want to play around with it, database creation should work now (if not with existing account you can create new one)

by seb711 1y ago

dataware-admin 1y ago

We don't think it is needed. Currently, the only thing which is stopping it from running on bare-metal no hypervisor are some drivers for virtual devices (eg. virtio net driver). Challenge is, ofc, supporting wide range of hardware options, but we don't intend to. We plan to support only modern x86_64 CPUs (arm is on the roadmap) and a select few NICs. Current implementation is written to be hosted on public cloud, so we implement what is needed for that, but in the future we intend to allow self hosted version, but only on selected server hardware. Now, if we have "big" server with like 256 cpus, etc. we can still split it many smaller "vms". Since the only code that runs with Hardware Manager is code we write, we can just add config options which pin execution to resources, eg. ram, we can just allow it to use from 4gb-8gb phys addr. Shared hardware like NIC is a bit trickier, but we do have some tricks up our sleeve which allow sharing.

seb711 1y ago
> which is stopping it from running on bare-metal no hypervisor are some drivers for virtual devices (eg. virtio net driver). why would you need to support virtual devices, if you are not in a virtualized environment?
- dataware-admin 1y ago
  Yea poor phrasing in that sentance. All code we have can already run on bare-metal except some drivers, since most are only for virtualized devices. Hopefuly that clears what we wanted to say. If we implement eg nic driver for physical device then we can run bare-metal no host at all.
  - seb711 1y ago
    Sounds great! This is the future!
    - dataware-admin 1y ago
      Glad you like it Btw, we fixed some whitelist issues and if you want to play around with it, database creation should work now (if not with existing account you can create new one)