On Mon, Jan 06, 2020 at 02:53:13PM -0600, Michael Catanzaro wrote:
On Mon, Jan 6, 2020 at 7:09 pm, Lennart Poettering
>- facebook is working on making oomd something that just works for
> everyone, they are in the final rounds of canonicalizing the
> configuration so that it can just work for all workloads without
> tuning. The last bits for this to be deployable are currently being
> done on the kernel side ("iocost"), when that's in, they'll
> oomd (or simplified parts of it) to systemd, so that it's just there
> and works. It's their expressive intention to make this something
> that also works for desktop stuff and requires no further
> tuning. they also will do the systemd work necessary. time frame:
> half a year, maybe one year, but no guarantees.
Asking around, I understand oomd only operates at the cgroup level,
i.e. it kills an entire cgroup at once, not individual processes. So
I understand this would also depend on GNOME-level work to ensure
individual applications get launched in their own systemd scopes,
I wanted to ask about this too... but didn't know where ;)
As of today, gnome-shell in F31 seems to start almost everything
as separate systemd user scopes:
- various services started automaticlly like /usr/libexec/gsd-power,
- flatpaks (this seems to be new, I had them running under
gnome-shell-wayland.service last week!)
Stuff started from the run dialog (alt-f2) and from
the overview still seems to land in gnome-shell-wayland.service,
but maybe this is fixed in gnome-shell 3.35?
Another issue is that things that are started through the gnome
terminal also land in gnome-terminal-server.service. They need to
get their own scopes to make resource allocation robust.
It seems we're quite close! Do we just need to wait for another
gnome release and then we'll have everything nicely segregated?