linux-kernel - Re: Linux machines dieing in swap storms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 26 Oct 2007 05:56:49 +0200
From:	Bodo Eggert <7eggert@....de>
To:	Rik van Riel <riel@...hat.com>, Richard Purdie <rpurdie@...ys.net>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux machines dieing in swap storms

Rik van Riel <riel@...hat.com> wrote:
> On Thu, 25 Oct 2007 16:20:41 +0100
> Richard Purdie <rpurdie@...ys.net> wrote:

>> Advice on solving this welcome preferably in mainline but I'll happily
>> hack my kernels with a workaround if need be.
> 
> I can't see any easy hacks or workarounds to fix the issue in the
> current MM, except maybe activate the OOM killer if the amount of
> page cache and buffer cache is really low and swap is full...
> 
> In the longer run, I'm working on:
> 
> http://linux-mm.org/PageReplacementDesign

What about only reclaimimn cache if the cache has grown beyond a watermark
and only reclaimimn non-cache if it's below another watermark? I can imagine
it will solve my diskcache-pushes-out-mousehandler problem, and I'm pretty
sure having very low file cache is bad for performance, too.

Another thing I can imagine is to detect thrashing conditions and to
change scheduling in order to increase the likehood of cache hits and
thereby progress: If an application just got a page, keep it running for
a while (accumulating negative credits).
-- 
"Of course, as admin, I can read all your email. But I am not THAT bored!"
        -- unknown author in comp.unix.aix

Friß, Spammer: 9w@...eggert.dyndns.org gNhwn@...z.7eggert.dyndns.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/