[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fedora-devel-list
Subject:    Re: Enable EarlyOOM on Fedora KDE - Fedora 33 Self-Contained Change proposal
From:       "Alexey A." <hakavlad () gmail ! com>
Date:       2020-07-19 9:01:21
Message-ID: CADrZ5ZWZt=kzTzE8jGFDS2Xh7paz1RE=vLV04jyB1SwvqKj7=g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


> Userspace isn't dead

If something looks like dead it is dead. A userspace that does not respond
to user actions is a dead userspace.

=D0=B2=D1=81, 19 =D0=B8=D1=8E=D0=BB. 2020 =D0=B3. =D0=B2 17:54, John M. Har=
ris Jr <johnmh@splentity.com>:

> On Sunday, July 19, 2020 1:47:23 AM MST Alexey A. wrote:
> > >Killing users' programs needlessly is not welcome
> >
> > Setting limits for cgroup (MemoryMax, MemorySwapMax) leads to "Killing
> > users' programs needlessly": system-wide available memory may be not
> > exhausted, but OOM killer will be invoked in this cgroup.
>
> I'm sure we can all agree that only killing off the software that people
> complain causes these events is better than killing off everything else
> just
> because the system doesn't have a ton of RAM available.
>
> > >The goal is to ensure the kernel can keep doing its job, it's
> > >not going to try to figure out what you intend for userspace, as well =
it
> > >shouldn't.
> >
> > The goal is to ensure the kernel can keep doing its job *and userspace*
> > doing its job. I don't need a system where the kernel is alive, but
> > userspace is dead.
>
> Userspace isn't dead when a system is thrashing. Your software is still
> running. If it gets killed, you're most likely going to lose your data.
>
> --
> John M. Harris, Jr.
>
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o=
rg
>

[Attachment #5 (text/html)]

<div dir="ltr">&gt; Userspace isn&#39;t dead<br><br>If something looks like dead it \
is dead. A userspace that does not respond to user actions is a dead \
userspace.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вс, \
19 июл. 2020 г. в 17:54, John M. Harris Jr &lt;<a \
href="mailto:johnmh@splentity.com">johnmh@splentity.com</a>&gt;:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">On Sunday, July 19, 2020 1:47:23 AM MST Alexey A. \
wrote:<br> &gt; &gt;Killing users&#39; programs needlessly is not welcome<br>
&gt; <br>
&gt; Setting limits for cgroup (MemoryMax, MemorySwapMax) leads to &quot;Killing<br>
&gt; users&#39; programs needlessly&quot;: system-wide available memory may be \
not<br> &gt; exhausted, but OOM killer will be invoked in this cgroup.<br>
<br>
I&#39;m sure we can all agree that only killing off the software that people <br>
complain causes these events is better than killing off everything else just <br>
because the system doesn&#39;t have a ton of RAM available.<br>
<br>
&gt; &gt;The goal is to ensure the kernel can keep doing its job, it&#39;s<br>
&gt; &gt;not going to try to figure out what you intend for userspace, as well it<br>
&gt; &gt;shouldn&#39;t.<br>
&gt; <br>
&gt; The goal is to ensure the kernel can keep doing its job *and userspace*<br>
&gt; doing its job. I don&#39;t need a system where the kernel is alive, but<br>
&gt; userspace is dead.<br>
<br>
Userspace isn&#39;t dead when a system is thrashing. Your software is still <br>
running. If it gets killed, you&#39;re most likely going to lose your data.<br>
<br>
-- <br>
John M. Harris, Jr.<br>
<br>
_______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: \
<a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" \
rel="noreferrer" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
 List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
 List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
 </blockquote></div>


[Attachment #6 (text/plain)]

_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


[prev in list] [next in list] [prev in thread] [next in thread]