From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bodo Eggert <7eggert@gmx.de>
Subject: Re: [PATCH 0/7] OMFS filesystem version 3
Date: Wed, 16 Apr 2008 11:56:43 +0200
Message-ID: <E1Jm4Ng-0000su-2j@be1.7eggert.dyndns.org>
References: <aiwLk-3mc-3@gated-at.bofh.it> <aiwLk-3mc-5@gated-at.bofh.it> <aiwLk-3mc-1@gated-at.bofh.it>
Reply-To: 7eggert@gmx.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
To: Anton Altaparmakov <aia21@cam.ac.uk>,
	Szabolcs Szakacsits <szaka@ntfs-3g.org>,
	Miklos Szeredi <miklos@szeredi.hu>, dwmw2@infradead.org,
	hch@infradead.org, me@bobcopeland.com,
	linux-k
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from moutng.kundenserver.de ([212.227.126.174]:57251 "EHLO
	moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1756107AbYDPJ7R (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Wed, 16 Apr 2008 05:59:17 -0400
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

Anton Altaparmakov <aia21@cam.ac.uk> wrote:
> On 14 Apr 2008, at 13:46, Szabolcs Szakacsits wrote:
>> On Mon, 14 Apr 2008 Anton Altaparmakov wrote:

>>> (and under no-one I include the OOM killer for example!)
>>
>> The OOM killer can be configured and if the fs still uses too much
>> memory
>> then probably it's better to be killed/restarted with journaling
>> support.
>> The important here would be the kernel finally fixing the non-sync
>> behavior
>> when it clams to do so (see recent kernel threads).
> 
> You don't get the point.  Any process in the system can be using too
> much memory and trigger the OOM killer even when the FS is behaving
> just fine...

Just set /proc/$pid/oom_adj to -17.