From: "Jim Sibley" <jlsibley@us.ibm.com>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: linux-kernel@vger.kernel.org, Giuliano Pochini <pochini@shiny.it>,
riel@conectiva.com.br
Subject: RE: Killing/balancing processes when overcommited
Date: Thu, 12 Sep 2002 12:00:33 -0700 [thread overview]
Message-ID: <OFDB91827C.152E85A4-ON88256C32.0067C0A4@boulder.ibm.com> (raw)
The mem eaters may not be the ones really "causing the problem" as
determined by the installation. The case where I discovered this was when
someone was asking for a lot of small chunks of memory (legitemately). So
you would need a history and a total memory usage to identify who this is.
And this is not really just limited to memory.
I still favor an installation file in /etc specifying the order in which
things are to be killed. Any alogrithmic assumptions are bound to fail at
some point to the dissatisfaction of the installation.
And this is not just limited to memory exhaustion. For example, if I exceed
the maximum number of files, I can't log on to fix the problem. If the
installation could set some priorities, they could say who to sacrifice in
order to keep others running.
Regards, Jim
Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs
t/l 543-4021, 408-463-4021, jlsibley@us.ibm.com
*** Grace Happens ***
next reply other threads:[~2002-09-12 18:58 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 19:00 Jim Sibley [this message]
2002-09-12 19:08 ` Killing/balancing processes when overcommited Thunder from the hill
2002-09-12 20:35 ` Alan Cox
2002-09-12 20:43 ` Thunder from the hill
2002-09-12 20:55 ` Alan Cox
2002-09-12 21:15 ` Thunder from the hill
2002-09-12 21:22 ` Jesse Pollard
2002-09-12 23:08 ` Alan Cox
2002-09-12 23:12 ` Thunder from the hill
2002-09-12 21:19 ` Jesse Pollard
2002-09-12 21:56 ` Thunder from the hill
2002-09-13 7:51 ` Giuliano Pochini
2002-09-13 10:17 ` Thunder from the hill
2002-09-12 19:09 ` Rik van Riel
2002-09-13 8:05 ` Giuliano Pochini
2002-09-13 10:54 ` Helge Hafting
2002-09-13 13:02 ` Giuliano Pochini
2002-09-13 16:40 ` Gerhard Mack
2002-09-13 20:23 ` Timothy D. Witham
-- strict thread matches above, loose matches on Subject: below --
2002-09-13 21:13 Jim Sibley
2002-09-13 22:31 ` Timothy D. Witham
2002-09-13 22:38 ` Timothy D. Witham
2002-09-13 22:44 ` Rik van Riel
2002-09-13 23:12 ` Timothy D. Witham
2002-09-16 7:29 ` Helge Hafting
2002-09-16 14:03 ` Rik van Riel
2002-09-16 18:49 ` Timothy D. Witham
2002-09-16 19:11 ` Rik van Riel
2002-09-16 20:27 ` Timothy D. Witham
2002-09-14 0:23 ` Jim Sibley
2002-09-12 18:14 Jim Sibley
2002-09-11 18:08 Jim Sibley
2002-09-11 18:27 ` Jurriaan
2002-09-12 8:26 ` Helge Hafting
2002-09-11 21:44 ` Alan Cox
2002-09-12 7:06 ` Tim Connors
2002-09-12 7:25 ` Giuliano Pochini
2002-09-12 16:02 ` Rik van Riel
2002-09-12 18:30 ` Thunder from the hill
2002-09-13 8:17 ` Giuliano Pochini
2002-09-13 10:22 ` Thunder from the hill
2002-09-13 12:53 ` Denis Vlasenko
2002-09-13 12:54 ` Jesse Pollard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OFDB91827C.152E85A4-ON88256C32.0067C0A4@boulder.ibm.com \
--to=jlsibley@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@shiny.it \
--cc=riel@conectiva.com.br \
--cc=thunder@lightweight.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).