• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: October 16th, 2025

help-circle






  • From the first paragraph:

    The panopticon is a design of institutional building with an inbuilt system of control, originated by the English philosopher and social theorist Jeremy Bentham in the 18th century. The concept is to allow all prisoners of an institution to be observed by a single prison officer, without the inmates knowing whether or not they are being watched.

    (emphasis mine)

    Bentham designed the Panopticon as a prison. It sounds like you’re using the word as a metaphor.

    I don’t think such a metaphorical usage is that great in this case. It works OK when you’re talking about big-brother style surveillance that is potentially present in your private life at all times (like the panopticon’s guard can potentially see any one inmate’s private activity at any time) but not when you’re talking about potentially being searched in a specific, limited, avoidable, circumventable circumstance.








  • sure, but how much memory? Here’s how I imagine it working (based on approximately zero knowledge):

    • OOM killer is triggered
    • The kernel code for the OOM killer (including heuristics) has to be swapped in. This code should only be a few KB at most so won’t actually take long.
    • The code has to be executed. To do so it needs to access information about all processes
    • Even if this information can be swapped out, it, likewise, is very small.

    So in my imagination it only takes two small blobs of data being swapped in - if kernel code and process information even can be swapped out; maybe it can be protected. Maybe you know something that ruins this picture though.



  • Isn’t this article essentially wrong because of this line:

    Ubuntu 26.10 also stops systemd-oomd being able to kill user sessions

    systemd-oomd works completely differently from the kernel OOM killer. Unless it’s changed, it just ranks everything by how much memory they’re using and picks the biggest memory hog that isn’t manually deprioritised by some config rule, and kills that. The OOM killer has a much smarter heuristic to deprioritise processes which are being actively used.

    As far as I understand, systemd-oomd was always a shoddy implementation because of this, and when it first started being used in Fedora (I don’t know about Ubuntu) also had insanely aggressive settings so that it would nobble something when you still had 20% free memory.

    The problem it was trying to solve was that Linux’s behaviour under memory pressure is actually abysmal. I have no idea if other OSes are any better, but basically once your computer starts thrashing, you’re better off rebooting it because it’ll be up again in a minute, whereas if you wait it’ll probably be half an hour if you’re lucky. The OOM killer detects actual out-of-memory, not thrashing, and so you can spend days slowly grinding your way through operations that should have taken seconds without ever triggering it. Hence systemd-oomd is designed to kick in before you actually run out of memory… and as a consequence it somewhat frequently does so too early.