Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Mar 2006 06:32:48 +1100
From:      Peter Jeremy <peterjeremy@optushome.com.au>
To:        Dmitry Pryanishnikov <dmitry@atlantis.dp.ua>
Cc:        Kostik Belousov <kostikbel@gmail.com>, Michael Proto <mike@jellydonut.org>, freebsd-stable@freebsd.org
Subject:   Re: RELENG_4 on flash disk and swap
Message-ID:  <20060310193248.GC688@turion.vk2pj.dyndns.org>
In-Reply-To: <20060310153737.X40396@atlantis.atlantis.dp.ua>
References:  <20060302181625.I3905@atlantis.atlantis.dp.ua> <76FAD2DB-CD18-42D4-95C8-F016CFB17B00@segpub.com.au> <20060303110936.R86586@atlantis.atlantis.dp.ua> <20060303185157.GB692@turion.vk2pj.dyndns.org> <20060304001224.G356@atlantis.atlantis.dp.ua> <20060304065138.GD692@turion.vk2pj.dyndns.org> <20060310121758.S80837@atlantis.atlantis.dp.ua> <20060310123942.GI37572@deviant.kiev.zoral.com.ua> <20060310153737.X40396@atlantis.atlantis.dp.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2006-Mar-10 15:53:43 +0200, Dmitry Pryanishnikov wrote:
> But AFAIK the kernel kills NOT the requesting process but the one with the
>largest RSS. This selection algorithm seems to be the dumbest one, since
>process with largest RSS almost always is the process which does some real 
>work.

This frees up the greatest amount of memory and so minimises the risk
of the problem recurring.

> Compare "never satisfy request" and "kill another, totally unrelated, 
>process".

This has been argued about many times in the past - though not with
any satisfactory solution AFAIK.  Look for 'SIGDANGER' in the archives.

-- 
Peter Jeremy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060310193248.GC688>