[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: Re: oom_adj
From: Jordi Polo <mumismo () gmail ! com>
Date: 2009-02-17 16:21:58
Message-ID: a4162420902170821u10549383ud9a4fc06609be05 () mail ! gmail ! com
[Download RAW message or body]
I am pretty confident that if someone can forward this to the kernel mailing
list some developers there will be very interested in the OOM making wrong
decisions in KDE pathology.
On Tue, Feb 17, 2009 at 11:40 PM, Lubos Lunak <l.lunak@suse.cz> wrote:
> On Saturday 14 of February 2009, John Tapsell wrote:
> > Hi all!
> >
> > We could identify important processes (xorg, kwin, krunner) that we
> > wouldn't want to be killed in a low memory situation, and adjust their
> > oom_adj property. This is used by the kernel out-of-memory handler
> > when it tries to kill processes because the system is low on memory.
> >
> > Thoughts?
>
> We already had this in KDE3: The OOM-murderer in Linux sucks in a special
> way
> when it comes to KDE, since it selects processes that launch other
> processes.
> That means kdeinit, and, in KDE4's case when there are many
> session-restored
> apps, also ksmserver. That also means there's no point in protecting KWin
> or
> KRunner, since those should never accumulate high enough score unless they
> are really broken. It is a question if we should and can protect Xorg,
> since
> the kernel can't tell which X client is the one creating too many X
> resources
> and causing Xorg to use a lot of memory.
>
> As for kdeinit, we had protection in KDE3, see
>
> http://websvn.kde.org/branches/KDE/3.5/kdelibs/kinit/start_kdeinit.c?view=log#rev579164,
> this commit and the following fixes could be ported to KDE4. At least I
> don't
> think that anything has changed since KDE3. Ksmserver could use something
> similar.
>
> --
> Lubos Lunak
> KDE developer
> --------------------------------------------------------------
> SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org
> Lihovarska 1060/12 tel: +420 284 028 972
> 190 00 Prague 9 fax: +420 284 028 951
> Czech Republic http://www.suse.cz
>
--
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org
[Attachment #3 (text/html)]
I am pretty confident that if someone can forward this to the kernel mailing list some \
developers there will be very interested in the OOM making wrong decisions in KDE \
pathology.<br><br><br><div class="gmail_quote">On Tue, Feb 17, 2009 at 11:40 PM, Lubos Lunak \
<span dir="ltr"><<a href="mailto:l.lunak@suse.cz">l.lunak@suse.cz</a>></span> wrote:<br> \
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt \
0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c">On Saturday 14 of \
February 2009, John Tapsell wrote:<br>
> Hi all!<br>
><br>
> We could identify important processes (xorg, kwin, krunner) that we<br>
> wouldn't want to be killed in a low memory situation, and adjust their<br>
> oom_adj property. This is used by the kernel out-of-memory handler<br>
> when it tries to kill processes because the system is low on memory.<br>
><br>
> Thoughts?<br>
<br>
</div></div> We already had this in KDE3: The OOM-murderer in Linux sucks in a special \
way<br> when it comes to KDE, since it selects processes that launch other processes.<br>
That means kdeinit, and, in KDE4's case when there are many session-restored<br>
apps, also ksmserver. That also means there's no point in protecting KWin or<br>
KRunner, since those should never accumulate high enough score unless they<br>
are really broken. It is a question if we should and can protect Xorg, since<br>
the kernel can't tell which X client is the one creating too many X resources<br>
and causing Xorg to use a lot of memory.<br>
<br>
As for kdeinit, we had protection in KDE3, see<br>
<a href="http://websvn.kde.org/branches/KDE/3.5/kdelibs/kinit/start_kdeinit.c?view=log#rev579164" \
target="_blank">http://websvn.kde.org/branches/KDE/3.5/kdelibs/kinit/start_kdeinit.c?view=log#rev579164</a> \
,<br> this commit and the following fixes could be ported to KDE4. At least I don't<br>
think that anything has changed since KDE3. Ksmserver could use something<br>
similar.<br>
<font color="#888888"><br>
--<br>
Lubos Lunak<br>
KDE developer<br>
--------------------------------------------------------------<br>
SUSE LINUX, s.r.o. e-mail: <a href="mailto:l.lunak@suse.cz">l.lunak@suse.cz</a> , <a \
href="mailto:l.lunak@kde.org">l.lunak@kde.org</a><br> Lihovarska 1060/12 tel: +420 284 \
028 972<br> 190 00 Prague 9 fax: +420 284 028 951<br>
Czech Republic <a href="http://www.suse.cz" \
target="_blank">http://www.suse.cz</a><br> </font></blockquote></div><br><br clear="all"><br>-- \
<br>Jordi Polo Carres<br>NLP laboratory - NAIST<br><a \
href="http://www.bahasara.org">http://www.bahasara.org</a><br><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic