{"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\/da\/blog\/news\/predstavlen-multikernel-mehanizm-dlya-odnovremennogo-vypolneniya-neskolkih-yader-linux","title":{"rendered":"Multikernel pr\u00e6senteret, en mekanisme til samtidig k\u00f8rsel af flere Linux kerner","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

For discussion, the Linux kernel developers have proposed a series of patches developed by the Multikernel project, which has recently been transitioned to open-source software 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 direct access to hardware resources and enabling the launch of several isolated system environments. The project was founded by Multikernel Technologies, led by Cong Wang, who oversees the Traffic Control (TC) subsystem in the Linux kernel. <\/p>\n

For launching and managing kernels, an improved call to kexec is proposed, which, unlike the classic kexec, is not limited to replacing the running kernel and allows for the launching of additional instances of the kernel that run in parallel. For monitoring and debugging the launched instances of the kernel, the interface \"\/proc\/multikernel\" is implemented, and for messaging between kernels and coordinating their work, the Multikernel IPI communication framework is proposed.

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

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

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

Performance using Multikernel is assessed to be close to that of execution on separate hardware. This has been achieved by eliminating the overhead typically associated with 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 launched environments is supported, ensuring predictable performance. <\/p>\n

Samtidig k\u00f8rsel af flere kerner foreg\u00e5r uden virtualisering, ved hj\u00e6lp af SMP-behandleren, der fordeler de tilg\u00e6ngelige CPU'er mellem instanser af Linux-kerner. Hver instans af Linux-kernerne er knyttet til en eller flere CPU-kerner, der er tildelt til dens k\u00f8rsel, mens de \u00f8vrige hardware-ressourcer deles. <\/p>\n

De vigtigste fordele ved Multikernel: <\/p>\n