News for hackers. Stuff that matters.
Re:L4Linux – Linux running on the L4 microkernel by aey on Saturday January 19, 2019 @01:19PM (#18948322)
Userspace would render its local window and send the invalidated regions to the kernel.

The problem was two fold. L4 ipc was just slower then a swi, and l4 driver model would lock the page table for every region instead of just checking every region all at once.

Re:L4Linux – Linux running on the L4 microkernel by microcolonel on Saturday January 19, 2019 @01:27PM (#18948365)
Which L4 was this, by the way? Did you replace it with an RTOS, a POSIX system?
Re:L4Linux – Linux running on the L4 microkernel by aey on Sunday January 20, 2019 @10:15AM (#18953377)
We had an internal bear metal implementation already.

L4 was just pushed as the “hotness”, and ironically as a way to get around the linux GPL issues at the time.

I don’t want to sound to critical. L4 is actually easier to build drivers for than Linux, and you are much less likely to shoot yourself in the foot.

It’s a great microckernel. It’s just that 4% may all come from the most human sensitive application.

Re:L4Linux – Linux running on the L4 microkernel by microcolonel on Sunday January 20, 2019 @01:43PM (#18954711)
I still can't tell what L4 you're talking about. I've heard that there are some pretty big differences in performance between other L4s and seL4, for example.
Re:L4Linux – Linux running on the L4 microkernel by alalo on Sunday January 20, 2019 @05:59PM (#18956170)
The 4% come from a application-level benchmark that was popular back then. This is about ARM9/armv5 too, which is not suited for any multi-user OS as address spaces switching is very expensive compared to today's architectures (armv6+) due to the needed cache flushing on every address space switch. This has nothing to do with L4 variants, this is an architectural issue.