this post was submitted on 07 Mar 2024
485 points (96.5% liked)

linuxmemes

20463 readers
477 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
485
Systemd controversy be like (sh.itjust.works)
submitted 5 months ago by loaExMachina to c/[email protected]
151 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] loutr 15 points 5 months ago (2 children)

The debate is as old as Linux itself, and well documented.

[–] [email protected] 7 points 5 months ago (1 children)

It doesn't seem to be a debate. "Microkernels are better" "yes but I don't have the time for it" but thanks

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

At a high level, microkernels push as much as possible into userspace, and monolithic kernels keep drivers in kernel space

There are arguments for each e.g. a buggy driver can’t write into the memory space of another driver as easily in a micro kernel, however it’s running in the same security level as userspace code. People will make arguments for both sides of which is more secure

Monolithic kernels also tended to be more performant at the time, as you didn’t have to context switch between ring 0 and ring 1 in the CPU to perform driver calls - we also regularly share memory directly between drivers

These days pretty much all kernels have moved to a hybrid kernel, as neither a truly monolithic kernel nor a truly micro kernel works outside of theoretical debates

[–] [email protected] 1 points 5 months ago

Thanks! I will look into