Главная
Study mode:
on
1
Intro
2
EDGE DEVICES WILL INCREASINGLY CONTAIN LINUX
3
THE INTELLIGENT EDGE REQUIRES REACTIVITY
4
IF EDGE DEVICES WILL CONTAIN LINUX, WHERE WILL THE REAL-TIME AND SAFETY WORKLOADS RUN?
5
USE CASE: KVM WITH CORE ISOLATION FOR TIME SENSITIVE NETWORKING
6
REALTIME AND SAFETY WORKLOADS WITH LINUX
7
WHY USE VIRTIO WORKLOAD INTEGRATION?
8
GENERALIZED HYPERVISOR-LESS VIRTIO ARCHITECTURE
9
SIMILARITIES / DIFFERENCES
10
HYPERVISOR-LESS VIRTIO SHARED MEMORY LAYOUT
11
HYPERVISOR-LESS VIRTIO SCENARIOS
12
VSOCK-ONLY HYPERVISOR-LESS VIRTIO
13
SIDE NOTE ON THE PERFORMANCE OF VIRTIO MMIO WITH MSIS WITH A HYPERVISOR
14
SIDE NOTE ON THE PERFORMANCE OF VIRTIO/PCI VS VIRTIO/MMIO WITH A HYPERVISOR
15
CONCLUSIONS
Description:
Explore hypervisor-less Virtio for real-time and safety applications in edge devices containing Linux. Learn about the increasing presence of Linux in edge devices, the need for reactivity in intelligent edge systems, and where real-time and safety workloads can be executed. Examine a use case involving KVM with core isolation for time-sensitive networking, and understand the benefits of Virtio workload integration. Dive into the generalized hypervisor-less Virtio architecture, comparing similarities and differences with traditional approaches. Study the shared memory layout and various scenarios for hypervisor-less Virtio implementation, including VSOCK-only configurations. Gain insights into performance considerations of Virtio MMIO with MSIs and Virtio/PCI vs Virtio/MMIO in hypervisor environments. Conclude with key takeaways on implementing hypervisor-less Virtio for real-time and safety-critical applications in edge computing.

Hypervisor-less Virtio for Real-time and Safety

Linux Foundation
Add to list
0:00 / 0:00