linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: chrisa@ultranet.com
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Nicolas Devillard <ndevilla@mygale.org>,
	linux-mm@kvack.org, Alan Cox <number6@the-village.bc.nu>
Subject: Re: memory overcommitment
Date: Wed, 19 Aug 1998 13:08:29 +0100	[thread overview]
Message-ID: <199808191208.NAA00888@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.00.9808181124250.6395-100000@chris.atenasio.net>

Hi,

On Tue, 18 Aug 1998 11:52:06 -0400 (EDT), Chris Atenasio
<root@lilo.dyn.ml.org> said:

>> If you can suggest a good algorithm for selecting processes to kill,
>> we'd love to hear about it.  The best algorithm will not be the same for
>> all users.

> How bout: if(no_more_ram) kill(process_using_most_ram());

Very simplistic: on many systems, that will mean starting gcc takes out
the X server. :-(

> Of course to be useful it would have to add together the usage of
> multiple instances of a program of the same uid(and then kill all of
> them too!).  Furthermore you might even want to kill uid 0 progs last.

Certainly.

One thing on the agenda for consideration in 2.3 is resident set size
limits and quotas, which will allow us to cleanly reserve enough swap
and physical memory for specific uses.

--Stephen
--
This is a majordomo managed list.  To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org

  reply	other threads:[~1998-08-19 13:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-17  8:46 Nicolas Devillard
1998-08-17 18:33 ` Stephen C. Tweedie
1998-08-18 15:52   ` Chris Atenasio
1998-08-19 12:08     ` Stephen C. Tweedie [this message]
1998-08-18 16:34   ` Nicolas Devillard
1998-08-19 12:07     ` Stephen C. Tweedie
1998-08-19 17:17       ` Nicolas Devillard

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=199808191208.NAA00888@dax.dcs.ed.ac.uk \
    --to=sct@redhat.com \
    --cc=chrisa@ultranet.com \
    --cc=linux-mm@kvack.org \
    --cc=ndevilla@mygale.org \
    --cc=number6@the-village.bc.nu \
    /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