On Mon, Dec 21, 2020 at 11:28:45AM -0500, Ben Cotton wrote:
> For memory pressure configuration, this will be
> ManagedOOMMemoryPressure=kill and ManagedOOMMemoryPressureLimit=4% on
> user@.service to have systemd-oomd send SIGKILLs to all processes
> under a selected cgroup when total memory
On Mon, Dec 28, 2020 at 7:30 PM Davide Cavalca via devel
wrote:
>
> On Mon, 2020-12-28 at 16:22 -0800, Kevin Fenzi wrote:
> > On Mon, Dec 28, 2020 at 07:44:04PM -, Tom Seewald wrote:
> > > > On Tue, Dec 22, 2020 at 6:17 PM Anita Zhang
> > > > > > >
> > > >
> > > > Another variation on this
On Mon, 2020-12-28 at 16:22 -0800, Kevin Fenzi wrote:
> On Mon, Dec 28, 2020 at 07:44:04PM -, Tom Seewald wrote:
> > > On Tue, Dec 22, 2020 at 6:17 PM Anita Zhang
> > > > >
> > >
> > > Another variation on this theme: enable by default in Fedora 34
> > > Server
> > > edition. And more
On Mon, Dec 28, 2020 at 07:44:04PM -, Tom Seewald wrote:
> > On Tue, Dec 22, 2020 at 6:17 PM Anita Zhang
> > >
> >
> > Another variation on this theme: enable by default in Fedora 34 Server
> > edition. And more broadly rolled out for Fedora 35.
> >
> > If it's broadly ready for Fedora
> On Tue, Dec 22, 2020 at 6:17 PM Anita Zhang wrote:
>
>
> Another variation on this theme: enable by default in Fedora 34 Server
> edition. And more broadly rolled out for Fedora 35.
>
> If it's broadly ready for Fedora 34, great. Otherwise, it seems like a
> good fit for Fedora Server
On Thu, Dec 24, 2020 at 06:01:51PM -0500, James Cassell wrote:
>
> On Tue, Dec 22, 2020, at 10:45 AM, Michael Catanzaro wrote:
> > Each gnome-terminal tab runs in its own cgroup:
> >
> > │ │ │ ├─app-org.gnome.Terminal.slice
> > │ │ │ │
> > ├─vte-spawn-1d1d5519-71d2-4035-929a-8a9ae5bc3822.scope
Am 21.12.20 um 17:45 schrieb Neal Gompa:
To revert back to earlyoom, run:
sudo systemctl disable --now systemd-oomd
sudo systemctl enable --now earlyoom
See man oomd.conf for configuration options.
What really makes me happy, if oomds keep clamd running, instead of
killing it, just
On Tue, Dec 22, 2020, at 10:45 AM, Michael Catanzaro wrote:
> Each gnome-terminal tab runs in its own cgroup:
>
> │ │ │ ├─app-org.gnome.Terminal.slice
> │ │ │ │
> ├─vte-spawn-1d1d5519-71d2-4035-929a-8a9ae5bc3822.scope
> │ │ │ │ │ ├─7848 bash
> │ │ │ │ │ └─7889 less /etc/hosts
> │ │ │ │
>
On Wed, Dec 23, 2020 at 12:32 pm, Vít Ondruch
wrote:
You see that I have executed FF from terminal. But I think that if
any other process running in the app-org.gnome.Terminal.slice starts
to grow memory usage, the whole tree will be killed.
systemd scopes get cgroups too, so only the scope
Dne 22. 12. 20 v 16:45 Michael Catanzaro napsal(a):
On Tue, Dec 22, 2020 at 10:45 am, Vít Ondruch
wrote:
And I wonder what will be the behavior for applications, which I
start from my terminal? The most typical example for me is running
GVim from gnome-terminal.
Each gnome-terminal tab
On Tue, Dec 22, 2020 at 6:17 PM Anita Zhang wrote:
> > That's why I think this change need to be postponed to Fedora 35 (opt-in
> > in F34 and default in F35).
>
> I'm actually not opposed to that.
Another variation on this theme: enable by default in Fedora 34 Server
edition. And more broadly
> Earlyoom maintainer here. I think it's too early to switch to
> systemd-oomd, because it was just merged to the systemd codebase and is
> still an experimental feature.
Hi! I authored the PR for systemd-oomd. It was merged as a feature for
"preview" rather than "release", but that was so the
On Tue, Dec 22, 2020 at 3:42 PM Tom Seewald wrote:
>
> > This is intended to be a generic approach to user space oom
> > management, but it does tie into resource control too. And the
> > resource control organization of what processes are considered
> > critical are different between a desktop
On Tue, Dec 22, 2020 at 10:41 pm, Tom Seewald
wrote:
So are you confirming that users are now going to need to place
things in their own cgroup if they do not want systemd-oomd to
potentially kill the single cgroup containing all of their running
applications?
If this change is approved:
On Tue, Dec 22, 2020, at 2:45 PM, Tom Seewald wrote:
> > If your desktop doesn't segregate apps and services into cgroups,
> > systemd-oomd will kill the entire desktop whenever anything uses too
> > much memory, because the desktop is going to be running in the same
> > cgroup as the apps
> This is intended to be a generic approach to user space oom
> management, but it does tie into resource control too. And the
> resource control organization of what processes are considered
> critical are different between a desktop and a server. The idea of
> "user wants to take control or see
On Tue, Dec 22, 2020 at 12:45 PM Tom Seewald wrote:
>
> > If your desktop doesn't segregate apps and services into cgroups,
> > systemd-oomd will kill the entire desktop whenever anything uses too
> > much memory, because the desktop is going to be running in the same
> > cgroup as the apps that
On Tue, Dec 22, 2020 at 7:45 pm, Tom Seewald wrote:
How will this work on headless systems like Fedora Server, Atomic,
and CoreOS? Will it be expected that users manually create their own
cgroups?
Either that, or don't use too much memory, yes. I assume SIGKILL is
probably at least somewhat
On Tue, Dec 22, 2020 at 11:42 AM Robbie Harwood wrote:
>
>
> I believe you are assuming the consequent when you suggest that kernel
> developers should be somehow fixing this in userspace.
>
> To back up: the described problem is the manifestation of an interaction
> between swap and the OOM
> If your desktop doesn't segregate apps and services into cgroups,
> systemd-oomd will kill the entire desktop whenever anything uses too
> much memory, because the desktop is going to be running in the same
> cgroup as the apps that it launches. So I think desktop spins (other
> than KDE)
On Tue, Dec 22, 2020 at 2:03 PM Michael Catanzaro wrote:
>
> On Tue, Dec 22, 2020 at 6:55 pm, Tom Seewald wrote:
> > Overall I like the change for desktop use, but I'm not sure it
> > currently is a good fit for non-Workstation/KDE spins of Fedora.
>
> If your desktop doesn't segregate apps and
On Tue, Dec 22, 2020 at 6:55 pm, Tom Seewald wrote:
Overall I like the change for desktop use, but I'm not sure it
currently is a good fit for non-Workstation/KDE spins of Fedora.
If your desktop doesn't segregate apps and services into cgroups,
systemd-oomd will kill the entire desktop
On Tue, Dec 22, 2020 at 1:41 pm, Robbie Harwood
wrote:
- OOM killer behavior. I think we're in agreement that this isn't the
thing that needs changed.
Let's back up. The choice is between earlyoom (status quo) or
systemd-oomd (future). We're not going to get rid of our userspace OOM
> On Mon, Dec 21, 2020 at 1:51 pm, Aleksei Bavshin wrote:
>
> Hm good point. I think only GNOME and KDE create systemd scopes when
> launching apps; systemd-oomd is not going to work well in other
> desktops. Probably other desktop spins should opt-out of this change
> for now.
>
> Michael
Dan Čermák writes:
> Robbie Harwood writes:
>
>> Ben Cotton writes:
>>
>>> For swap based actions, systemd-oomd will monitor the system-wide swap
>>> space and act when available swap falls below the configured
>>> threshold, starting with the cgroups with the highest swap usage to
>>> the
Robbie Harwood writes:
> Ben Cotton writes:
>
>> For swap based actions, systemd-oomd will monitor the system-wide swap
>> space and act when available swap falls below the configured
>> threshold, starting with the cgroups with the highest swap usage to
>> the least. Keeping some amount of
Ben Cotton writes:
> For swap based actions, systemd-oomd will monitor the system-wide swap
> space and act when available swap falls below the configured
> threshold, starting with the cgroups with the highest swap usage to
> the least. Keeping some amount of swap (if enabled) available will
>
On Tue, Dec 22, 2020 at 10:45 am, Vít Ondruch
wrote:
And I wonder what will be the behavior for applications, which I
start from my terminal? The most typical example for me is running
GVim from gnome-terminal.
Each gnome-terminal tab runs in its own cgroup:
│ │ │
On 21.12.2020 17:28, Ben Cotton wrote:
Provide a better experience for Fedora users in out-of-memory (OOM)
situations by enabling systemd-oomd by default.
Earlyoom maintainer here. I think it's too early to switch to
systemd-oomd, because it was just merged to the systemd codebase and is
Dne 21. 12. 20 v 23:20 Aleksei Bavshin napsal(a):
On 12/21/20 1:53 PM, Neal Gompa wrote:
On Mon, Dec 21, 2020 at 4:52 PM Aleksei Bavshin
wrote:
On 12/21/20 8:28 AM, Ben Cotton wrote:
== Documentation ==
https://www.freedesktop.org/software/systemd/man/systemd-oomd.html/>
On Mon, Dec 21, 2020 at 2:20 pm, Aleksei Bavshin
wrote:
It's just that as a maintainer of one of those alternative desktop
environments I have no idea how to make that work in default
configuration.
You're going to want to create a new systemd scope for each application
that you launch.
On 12/21/20 1:53 PM, Neal Gompa wrote:
On Mon, Dec 21, 2020 at 4:52 PM Aleksei Bavshin wrote:
On 12/21/20 8:28 AM, Ben Cotton wrote:
== Documentation ==
https://www.freedesktop.org/software/systemd/man/systemd-oomd.html
https://www.freedesktop.org/software/systemd/man/oomctl.html
On Mon, Dec 21, 2020 at 1:51 pm, Aleksei Bavshin
wrote:
This makes me slightly very concerned. According to cgls, I have most
of the apps running directly under user-$UID.slice ->
session-X.scope. That includes a compositor (sway) and a few
applications that consume uncomfortably close to
On Mon, Dec 21, 2020 at 4:52 PM Aleksei Bavshin wrote:
>
>
>
> On 12/21/20 8:28 AM, Ben Cotton wrote:
> > == Documentation ==
> >
> > https://www.freedesktop.org/software/systemd/man/systemd-oomd.html
> > https://www.freedesktop.org/software/systemd/man/oomctl.html
> >
On 12/21/20 8:28 AM, Ben Cotton wrote:
== Documentation ==
https://www.freedesktop.org/software/systemd/man/systemd-oomd.html
https://www.freedesktop.org/software/systemd/man/oomctl.html
https://www.freedesktop.org/software/systemd/man/oomd.conf.html
Be aware that if you intend to enable
On Mon, Dec 21, 2020 at 2:35 PM Anita Zhang wrote:
>
> I think so. I designed the systemd-oomd interface to be general enough to
> eventually support sending d-bus signals in addition to or in place of
> killing cgroups with SIGKILL. But I'm uncertain if it can be implemented
> before the
On Mon, 2020-12-21 at 12:44 -0600, Michael Catanzaro wrote:
> On Mon, Dec 21, 2020 at 9:59 am, Davide Cavalca via devel
> wrote:
> > We had thought about that, but one concern was migrating custom
> > configuration that one might have for earlyoom, which could be
> > tricky.
> > If we're ok with
I think so. I designed the systemd-oomd interface to be general enough to
eventually support sending d-bus signals in addition to or in place of killing
cgroups with SIGKILL. But I'm uncertain if it can be implemented before the
freeze.
___
devel
On Mon, Dec 21, 2020 at 9:59 am, Davide Cavalca via devel
wrote:
We had thought about that, but one concern was migrating custom
configuration that one might have for earlyoom, which could be tricky.
If we're ok with unconditionally migrating to oomd with its default
config, that should be
On Mon, Dec 21, 2020 at 12:59 PM Davide Cavalca via devel
wrote:
>
> On Mon, 2020-12-21 at 10:57 -0600, Michael Catanzaro wrote:
> > On Mon, Dec 21, 2020 at 11:28 am, Ben Cotton
> > wrote:
> > > == Upgrade/compatibility impact ==
> > >
> > > Existing systems running earlyoom will not be
On Mon, 2020-12-21 at 10:57 -0600, Michael Catanzaro wrote:
> On Mon, Dec 21, 2020 at 11:28 am, Ben Cotton
> wrote:
> > == Upgrade/compatibility impact ==
> >
> > Existing systems running earlyoom will not be modified. One can
> > transition to systemd-oomd via:
> >
> > sudo systemctl disable
On Mon, Dec 21, 2020 at 11:28 am, Ben Cotton wrote:
== Upgrade/compatibility impact ==
Existing systems running earlyoom will not be modified. One can
transition to systemd-oomd via:
sudo systemctl disable --now earlyoom
sudo systemctl enable --now systemd-oomd
Systems that were previously
On Mon, Dec 21, 2020 at 11:29 AM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
>
> == Summary ==
>
> Provide a better experience for Fedora users in out-of-memory (OOM)
> situations by enabling
> [https://www.freedesktop.org/software/systemd/man/systemd-oomd.html
43 matches
Mail list logo
