On 1/7/20 11:07 AM, Benjamin Berg wrote:
On Tue, 2020-01-07 at 09:47 +0000, Zbigniew Jędrzejewski-Szmek
wrote:
> On Mon, Jan 06, 2020 at 02:53:13PM -0600, Michael Catanzaro wrote:
>> On Mon, Jan 6, 2020 at 7:09 pm, Lennart Poettering
>> <mzerqung(a)0pointer.de> wrote:
>>> - 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 submit
>>> 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,
>> yes?
>
> 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,
> /usr/libexec/gsd-sound, etc.
>
> - flatpaks (this seems to be new, I had them running under
> gnome-shell-wayland.service last week!)
Hmm, pretty sure flatpaks have always created their own scopes.
> 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?
This should have changed with the gnome-shell 3.34.2 update in Fedora
31. It may be that it has not reached rawhide yet though.
Just had a look at awesome, all applications seem to be in the same
cgroup, according to systemd-cgtop. Thus if the whole cgroup would be
killed, that means rather then stopping firefox if it uses to much
memory, my whole session would be terminated.
>> 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.
>
> Do you think we should just place each VT into its own scope?
>
> That seems like a reasonable start in principle, though graphical
> applications launched from the terminal may still not be moved into
> their own scope then.
>
>> It seems we're quite close! Do we just need to wait for another
>> gnome release and then we'll have everything nicely segregated?
>
> Likely not perfect, but hopefully close enough for many purposes :)
>
> Benjamin