|
|
Subscribe / Log in / New account

The Debian init system general resolution returns

The Debian init system general resolution returns

Posted Oct 25, 2014 6:38 UTC (Sat) by viro (subscriber, #7872)
In reply to: The Debian init system general resolution returns by johannbg
Parent article: The Debian init system general resolution returns

Look, mount table is trivial to build from scratch - open /proc/self/mountinfo and read it; check the code in systemd that does this work. Moreover, keeping it updated is also easy - check the same code.
It's not really worth bothering with any IPC, let alone the one of push instead of pull variety.

And if you do insist on IPC, for some reason, you could bloody well start a caching daemon on demand (with e.g. timeout for inactivity). There's no reason whatsoever to keep that in PID 1 or anywhere near it.

We already have mechanisms for parallelizing. Had them for more than four decades. Called "processes"...

Having systemd forwarding a bunch of stuff it gleans from the kernel is asking for bottlenecks, for no good reason. System calls are not going away; not unless you want a truly monumental bottleneck with systemd playing the role of Mach server. Even then read(2) and open(2) wouldn't disappear, including those of /proc/self/mountinfo...


to post comments

The Debian init system general resolution returns

Posted Oct 25, 2014 8:40 UTC (Sat) by johannbg (guest, #65743) [Link] (1 responses)

You do realize when I spoke about parallelizing I was referring to daemon start-ups and states etc ( and signal handling there of ).

We have to agree to disagree on the push vs pull implementation.

The Debian init system general resolution returns

Posted Oct 25, 2014 19:23 UTC (Sat) by dlang (guest, #313) [Link]

systemd is not the only way to address parallel startup


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds