{"id":143961,"date":"2025-09-20T17:11:55","date_gmt":"2025-09-20T15:11:57","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/predstavlen-multikernel-mehanizm-dlya-odnovremennogo-vypolneniya-neskolkih-yader-linux"},"modified":"2026-02-16T13:24:20","modified_gmt":"2026-02-16T11:24:20","slug":"predstavlen-multikernel-mehanizm-dlya-odnovremennogo-vypolneniya-neskolkih-yader-linux","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/predstavlen-multikernel-mehanizm-dlya-odnovremennogo-vypolneniya-neskolkih-yader-linux","title":{"rendered":"Multikernel has been introduced, a mechanism for simultaneously running multiple Linux kernels.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

To discuss with Linux kernel developers, a series of patches has been proposed, developed by the Multikernel project, which has recently been transitioned to open-source status and will now be developed collaboratively with the community. Multikernel allows multiple independent instances of the Linux kernel to run on a single physical computer, granting them direct access to hardware resources and enabling the operation of several isolated system environments. The project was created by Multikernel Technologies, founded and led by Cong Wang, who oversees the traffic control subsystem (TC) within the Linux kernel. <\/p>\n

An enhanced call to kexec has been proposed to launch and manage kernels. Unlike the classic kexec, this version is not limited to replacing the running kernel; it allows for launching additional kernel instances that can run in parallel. An interface at \"\/proc\/multikernel\" has been implemented for monitoring and debugging the running kernel instances, while a communication framework called Multikernel IPI has been introduced for messaging between kernels and coordinating their operations.

\"Multikernel<\/center> <\/p>\n

Multikernel is presented as a new isolation architecture that occupies a niche between hypervisor-based virtualization and container-based isolation using a shared kernel. Unlike virtualization, Multikernel does not require the use of a hypervisor, simplifies the creation of environments for isolated execution of individual applications, and achieves high performance without the overhead associated with virtualization. In contrast to containers, Multikernel provides a high level of isolation<\/a> and allows for the use of a separate kernel in each isolated environment.

\"Multikernel<\/center> <\/p>\n

Performance when using Multikernel is assessed as being close to that of execution on dedicated hardware. This has been achieved by eliminating the overhead typical of virtualization, which arises from control transfer handlers between virtual machines (VM exit), IOMMU translation, and hypervisor intervention in the execution of privileged operations. Dynamic resource allocation for the environments being launched is supported, ensuring predictable performance. <\/p>\n

Simultaneous execution of multiple kernels occurs without virtualization, using an SMP handler that distributes available CPUs among instances of Linux kernels. Each Linux kernel instance is assigned one or more CPUs designated for its execution while sharing the remaining hardware resources. <\/p>\n

Key advantages of Multikernel: <\/p>\n