From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: Re: What's the NFS OOM problem? Date: Thu, 17 Aug 2006 15:04:29 +1000 Message-ID: <17635.63709.848914.895135@cse.unsw.edu.au> References: <4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com> <20060810045711.GI8776@1wt.eu> <17627.53340.43470.60811@cse.unsw.edu.au> <44E21166.60308@atipa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Willy Tarreau , Xin Zhao , linux-kernel , linux-fsdevel@vger.kernel.org Return-path: Received: from cantor2.suse.de ([195.135.220.15]:42473 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932403AbWHQFEh (ORCPT ); Thu, 17 Aug 2006 01:04:37 -0400 To: Roger Heflin In-Reply-To: message from Roger Heflin on Tuesday August 15 Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tuesday August 15, rheflin@atipa.com wrote: > > I have noticed on SLES kernels that when the dirty_*ratios turned down it > still uses alot more memory than it should work writeback buffers, it makes > me think that with the default setting of 40% that it for some reason > may be using all of memory and deadlocking. It does not seem like an > NFS only issue, as I believe I have duplicated it with a fast lock > setup. We seem to have a little patch in SuSE kernels that might be making the problem worse .... though I presume it was introduced for a reason. I haven't managed to track what that reason was yet. What is "a fast lock setup"?? I don't understand. NeilBrown