multikernel.io/index.html at main · multikernel/multikernel.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
---
layout: default
title: "Multikernel Technologies - Split-Kernel Architecture for Linux"
description: "The Multikernel split-kernel architecture offloads device drivers and interrupt processing to a dedicated kernel, delivering isolation and native performance without a hypervisor."
---

<main>
    <!-- Hero Section -->
    <section class="hero">
        <div class="hero-container">
            <div class="hero-badge">
                <i data-lucide="cpu"></i>
                <span>Split-Kernel Architecture</span>
            </div>

            <h1>The Foundation for Isolated, High-Performance Linux</h1>
            <p class="subtitle">The Multikernel system offloads all device drivers and I/O processing to a dedicated kernel, enabling applications to run in isolated kernels on dedicated cores with performance indistinguishable from bare metal.</p>

            <div class="button-group">
                <a href="/technology.html" class="btn btn-primary">
                    <i data-lucide="cpu"></i>
                    How It Works
                </a>
                <a href="/getting-started.html" class="btn btn-secondary">
                    <i data-lucide="rocket"></i>
                    Get Started
                </a>
            </div>

            <div class="hero-trust">
                <p class="trust-text">Built on upstream Linux, 100% open source</p>
                <div class="trust-features">
                    <div class="trust-feature">
                        <i data-lucide="shield-check"></i>
                        <span>Kernel-Level Isolation</span>
                    </div>
                    <div class="trust-feature">
                        <i data-lucide="zap"></i>
                        <span>Native Performance</span>
                    </div>
                    <div class="trust-feature">
                        <i data-lucide="refresh-cw"></i>
                        <span>Zero-Downtime Updates</span>
                    </div>
                    <div class="trust-feature">
                        <i data-lucide="github"></i>
                        <span>Open Source</span>
                    </div>
                </div>
            </div>
        </div>
    </section>

    <!-- Why Split-Kernel -->
    <section id="value-proposition" class="value-section">
        <div class="section-container">
            <div class="value-content">
                <div class="value-text">
                    <div class="section-badge">
                        <i data-lucide="layers"></i>
                        <span>Why Split-Kernel</span>
                    </div>
                    <h2 class="section-title">Isolation Built into the Architecture</h2>
                    <p class="section-subtitle">In a traditional Linux kernel, application code and device processing compete for the same CPU cores. The split-kernel architecture removes this contention by offloading all device processing to a dedicated kernel on dedicated cores. Applications see zero interrupts, not because of tuning, but because interrupts physically cannot reach them.</p>

                    <div class="value-cta">
                        <a href="/technology.html" class="btn-link">
                            Learn more about the architecture
                            <i data-lucide="arrow-right"></i>
                        </a>
                    </div>
                </div>

                <div class="value-visual">
                    <div class="performance-chart">
                        <div class="chart-title">Traditional: One Kernel, All Contexts</div>
                        <div class="chart-bars">
                            <div class="chart-bar">
                                <div class="bar-fill" style="height: 40%"></div>
                                <div class="bar-label">App</div>
                            </div>
                            <div class="chart-bar">
                                <div class="bar-fill" style="height: 30%"></div>
                                <div class="bar-label">Syscall</div>
                            </div>
                            <div class="chart-bar">
                                <div class="bar-fill multikernel" style="height: 30%"></div>
                                <div class="bar-label">IRQ/softirq</div>
                            </div>
                        </div>
                        <div class="chart-improvement">Interrupts steal app CPU cycles</div>
                    </div>
                </div>
            </div>
        </div>
    </section>

    <!-- Key Components -->
    <section id="capabilities">
        <div class="section-container">
            <div class="section-header">
                <div class="section-badge">
                    <i data-lucide="cpu"></i>
                    <span>Key Components</span>
                </div>
                <h2 class="section-title">The Multikernel System</h2>
                <p class="section-subtitle">A combination of dedicated app-kernels, a shared device-kernel, and high-speed shared memory that enables stronger isolation, faster innovation, and enhanced security.</p>
            </div>

            <div class="cards-grid">
                <div class="capability-card primary">
                    <div class="capability-icon">
                        <i data-lucide="monitor"></i>
                    </div>
                    <h3 class="capability-title">App-Kernels</h3>
                    <p class="capability-description">Each application runs in its own Linux kernel on dedicated cores. Interrupts and device drivers are absent from these kernels entirely. Practically all compute resources are delivered to the application.</p>
                    <div class="capability-features">
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Dedicated cores per workload</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Zero interrupt overhead</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Minimal attack surface</span>
                        </div>
                    </div>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="hard-drive"></i>
                    </div>
                    <h3 class="capability-title">Device-Kernel</h3>
                    <p class="capability-description">All device drivers and I/O processing are offloaded to a dedicated device-kernel running on its own cores. This kernel serves every app-kernel and can be updated or replaced independently.</p>
                    <div class="capability-features">
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>All drivers and interrupts contained</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Independent update lifecycle</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Driver fault isolation</span>
                        </div>
                    </div>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="database"></i>
                    </div>
                    <h3 class="capability-title">DAXFS Shared Memory</h3>
                    <p class="capability-description">Kernels communicate through DAXFS, a shared-memory filesystem with zero-copy data transfer. No network round trips, no serialization overhead.</p>
                    <div class="capability-features">
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Zero-copy data path</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Lock-free coordination</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Shared page cache</span>
                        </div>
                    </div>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="refresh-cw"></i>
                    </div>
                    <h3 class="capability-title">Independent Lifecycle</h3>
                    <p class="capability-description">Each kernel instance has its own update path, its own failure domain, and its own rollback capability. Update the device-kernel without restarting a single application.</p>
                    <div class="capability-features">
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Zero-downtime kernel updates</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Per-kernel fault domains</span>
                        </div>
                        <div class="feature-item">
                            <i data-lucide="check"></i>
                            <span>Instant rollback</span>
                        </div>
                    </div>
                </div>
            </div>
        </div>
    </section>

    <!-- Benefits -->
    <section id="benefits">
        <div class="section-container">
            <div class="section-header">
                <h2 class="section-title">Benefits</h2>
            </div>

            <div class="cards-grid">
                <div class="capability-card primary">
                    <div class="capability-icon">
                        <i data-lucide="shield-check"></i>
                    </div>
                    <h3 class="capability-title">Enhanced Security</h3>
                    <p class="capability-description">By offloading device drivers to a dedicated kernel, the attack surface of each app-kernel is minimized. A driver vulnerability in the device-kernel cannot access app-kernel memory. Device code is structurally absent from app-kernels, eliminating an entire class of attack vectors.</p>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="zap"></i>
                    </div>
                    <h3 class="capability-title">Better Performance and Efficiency</h3>
                    <p class="capability-description">The Multikernel system delivers practically all compute and memory resources of the host to your application. App-kernels have no interrupt overhead and no resource contention with drivers. Performance is indistinguishable from a dedicated machine.</p>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="refresh-cw"></i>
                    </div>
                    <h3 class="capability-title">Faster Innovation</h3>
                    <p class="capability-description">Update the device-kernel without restarting a single application. Roll back a bad driver update instantly. Each kernel has its own lifecycle, enabling teams to ship infrastructure and application changes on their own schedules.</p>
                </div>

                <div class="capability-card">
                    <div class="capability-icon">
                        <i data-lucide="cloud"></i>
                    </div>
                    <h3 class="capability-title">No Nested Virtualization</h3>
                    <p class="capability-description">The Multikernel system provides kernel-level isolation inside any standard cloud VM without nested virtualization. No special instance types, no hypervisor overhead. Deploy on AWS, GCP, or Azure with the isolation of separate kernels and the performance of bare metal.</p>
                </div>
            </div>
        </div>
    </section>
</main>