mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Jeremy Linton <jlinton@interactivesi.com>
Cc: Stephen Satchell <satch@fluent-access.com>, linux-kernel@vger.kernel.org
Subject: Re: Ongoing 2.4 VM suckage
Date: Tue, 7 Aug 2001 09:51:12 +0200	[thread overview]
Message-ID: <20010807095112.Q6387@khan.acc.umu.se> (raw)
In-Reply-To: <007801c11c67$87d55980$b6562341@cfl.rr.com> <4.3.2.7.2.20010803225855.00bc2a60@mail.fluent-access.com> <02a101c11e96$45db1d40$bef7020a@mammon>
In-Reply-To: <02a101c11e96$45db1d40$bef7020a@mammon>; from jlinton@interactivesi.com on Mon, Aug 06, 2001 at 11:37:53AM -0500

On Mon, Aug 06, 2001 at 11:37:53AM -0500, Jeremy Linton wrote:
> From: "Stephen Satchell" <satch@fluent-access.com>
> > At 07:08 PM 8/3/01 -0300, you wrote:
> > >On Fri, 3 Aug 2001, Mike Black wrote:
> > >
> > > > Couldn't kswapd just gracefully back-off when it doesn't make any
> > > > progress? In my case (with ext3/raid5 and a tiobench test) kswapd
> > > > NEVER actually swaps anything out. It just chews CPU time.
> > >
> > > > So...if kswapd just said "didn't make any progress...*2 last sleep" so
> > > > it would degrade itself.
> > >
> > >It wouldn't just degrade itself.
> > >
> > >It would also prevent other programs in the system
> > >from allocating memory, effectively halting anybody
> > >wanting to allocate memory.
> Big snip...
> 
> > To the rest of the kernel list:  apologies for taking up so much space
> with
> > a userland issue.  The thing is, in the months I've seen the VM problem
> > discussed, and the "zillionth person to complain about it," I haven't seen
> > any pointer to any discussion about how userland programs can insulate
> > themselves from being killed when they try to use up too much
> > RAM.  Commercial quality programs, and programs wanting to use as much of
> > the resources as possible to minimize run times, need to monitor what they
> > are doing to the system and pull back when they tread toward suicide.
> >
> > Put another way, people should NOT use safety nets as the only means of
> > breaking a fall.
>     AIX, also allows something similar to linux's over commit. Right before
> its OOM killer fires it sends the target process(es) a non standard signal
> (can't remember what its called) which indicates that if the process
> continues to allocate memory it runs the risk of being killed.

SIGDANGER

> I'm not advocating this idea, only presenting it as a solution other people
> have implemented to work around broken VM issues.

I consider SIGDANGER to work very well.


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-08-07  7:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 18:29 Jeffrey W. Baker
2001-08-02 18:52 ` Richard B. Johnson
2001-08-02 19:10   ` Jeffrey W. Baker
2001-08-02 19:54     ` Richard B. Johnson
2001-08-02 20:10       ` Jeffrey W. Baker
2001-08-02 20:16         ` Rik van Riel
2001-08-02 20:28           ` Rik van Riel
2001-08-03 17:59             ` David Ford
2001-08-03 20:53               ` Rik van Riel
2001-08-03 21:59                 ` Mike Black
2001-08-03 22:08                   ` Rik van Riel
2001-08-04  1:06                     ` Daniel Phillips
2001-08-03 23:58                   ` [PATCH] Disable kswapd through proc (was Ongoing 2.4 VM suckage) Daniel Phillips
2001-08-04  7:21                   ` Ongoing 2.4 VM suckage Stephen Satchell
2001-08-06  8:55                     ` Helge Hafting
2001-08-06 16:37                     ` Jeremy Linton
2001-08-07  7:51                       ` David Weinehall [this message]
2001-08-03 22:47                 ` David Ford
2001-08-02 21:01         ` Richard B. Johnson
2001-08-02 21:11           ` Jeffrey W. Baker
2001-08-02 21:44             ` Jakob Østergaard
2001-08-02 21:52               ` Jeffrey W. Baker
2001-08-02 21:56                 ` Miles Lane
2001-08-02 22:05                   ` Jeffrey W. Baker
2001-08-02 22:07                 ` Rik van Riel
2001-08-02 22:17                   ` Jeffrey W. Baker
2001-08-02 22:27                     ` Rik van Riel
2001-08-02 22:32                       ` Jeffrey W. Baker
2001-08-02 22:56                       ` BERECZ Szabolcs
2001-08-03 13:07                       ` jlnance
2001-08-03 13:31                         ` Richard B. Johnson
2001-08-06 13:22                         ` Luigi Genoni
2001-08-06 13:29                         ` David S. Miller
2001-08-02 23:46                     ` Ongoing 2.4 VM suckage pagemap_lru_lock Jeremy Linton
2001-08-02 22:15                 ` Ongoing 2.4 VM suckage Pavel Zaitsev
2001-08-02 22:20                 ` Jakob Østergaard
2001-08-03 12:04 ` Anders Peter Fugmann
2001-08-03 16:03   ` Rik van Riel
2001-08-03 16:24     ` Anders Peter Fugmann
2001-08-03 21:24       ` Rik van Riel
2001-08-03 22:00         ` Anders Peter Fugmann

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=20010807095112.Q6387@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=jlinton@interactivesi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=satch@fluent-access.com \
    /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

all inboxes | Powered by JetHome®