Live data from Hacker News

L4Linux – Linux running on the L4 microkernel

l4linux.org

41–42 of 42 posts

Re: L4Linux – Linux running on the L4 microkernel

#41
post #10

Okay, can someone explain why is this a thing? It is a genuine question. I am not very familiar with OS designs and skimming through the landing page didn't help. Is it essentially a Linux kernel that runs within an existing instance of Linux? Why is it important/useful? Thanks.

The idea was to have something you would call microservice architecture today, just for OS functions. An ethernet driver server application would talk to an IP server, which would talk to a TCP server that distributes messages to the applications. The kernel would just isolate all those applications and enable communication between them. If the ethernet driver daemon crashed you would just restart it.

The communication overhead remained a problem for microkernels, despite L4's achievements in that area. The advantages were somewhat overstated. The complexity merely moved from the kernel into the applications. A security bug in the IP driver daemon can still compromise the whole system, just like a driver in a monolithic kernel.

Re: L4Linux – Linux running on the L4 microkernel

#42
post #2

Anyone used this before? If it supports arm it could be a handy system.

Can I ask what you'll find it useful for? The technology is neat, I'm just struggling to think of something that would benefit from it.

Primarily for soft (or hard) real time operations. Even kernel modules running in a RT-Linux have a difficult time responding consistently to an IRQ at sub-10 uS latency. Of course, the larger SoC capable of running Linux can have hardware latencies due to shared data buses, etc. but still having a RTOS layer “underneath” Linux would be a good way to ensure more consistent responses.
Post reply on HN