Proceedings of the ACM Symposium on Cloud Computing 2018
DOI: 10.1145/3267809.3267845
|View full text |Cite
|
Sign up to set email alerts
|

Unikernels as Processes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
20
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 42 publications
(20 citation statements)
references
References 18 publications
0
20
0
Order By: Relevance
“…To strengthen and expand the capability of our framework, we plan on offloading non-virtualised EF. Unikernels do not actually require a virtual hardware abstraction; they can achieve similar levels of isolation when running as processes by taking advantage of existing kernel system call whitelisting mechanisms as demonstrated in [22]. This has the potential to make our system compatible with a larger range of devices and enable a much simpler integration of existing tools into our platform.…”
Section: Discussionmentioning
confidence: 99%
“…To strengthen and expand the capability of our framework, we plan on offloading non-virtualised EF. Unikernels do not actually require a virtual hardware abstraction; they can achieve similar levels of isolation when running as processes by taking advantage of existing kernel system call whitelisting mechanisms as demonstrated in [22]. This has the potential to make our system compatible with a larger range of devices and enable a much simpler integration of existing tools into our platform.…”
Section: Discussionmentioning
confidence: 99%
“…To make it even more interesting, recent nding shows that Unikernels do not require a virtual hardware abstraction. It can directly run as a process by exploiting an existing kernel system that is called whitelisting mechanism (Williams et al 2018). Looking into the combination features of virtual machine and container in one single virtualization technology, we can hope for the be er multi-tenancy for work ow as a service platform using this technology.…”
Section: Multiple Workflows Scheduling In Multi-tenant Distributed Symentioning
confidence: 99%
“…A container, on the other hand, interacts with the host system via the kernel system call interface. There is a huge difference in the width of these interfaces: there are over 300 different system calls in Linux in contrast to the about twenty different hypercalls in the Xen hypervisor interface [83]. This makes it much easier to monitor and control the hypercalls in a VM compared to the systems calls in a container-based platform.…”
Section: Security Aspectsmentioning
confidence: 99%