linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Roger Heflin <rheflin@atipa.com>
Cc: Willy Tarreau <w@1wt.eu>, Xin Zhao <uszhaoxin@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: What's the NFS OOM problem?
Date: Thu, 17 Aug 2006 15:04:29 +1000	[thread overview]
Message-ID: <17635.63709.848914.895135@cse.unsw.edu.au> (raw)
In-Reply-To: message from Roger Heflin on Tuesday August 15

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

  reply	other threads:[~2006-08-17  5:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08 22:24 What's the NFS OOM problem? Xin Zhao
2006-08-09  2:33 ` H. Peter Anvin
2006-08-10  4:57 ` Willy Tarreau
2006-08-10 21:53   ` Grant Coady
2006-08-11  0:33   ` Neil Brown
2006-08-11  3:57     ` Willy Tarreau
2006-08-11  4:24       ` Neil Brown
2006-08-11  8:48     ` Peter Zijlstra
2006-08-14  2:03       ` Neil Brown
2006-08-15 18:24     ` Roger Heflin
2006-08-17  5:04       ` Neil Brown [this message]
2006-08-17 13:29         ` Roger Heflin

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=17635.63709.848914.895135@cse.unsw.edu.au \
    --to=neilb@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rheflin@atipa.com \
    --cc=uszhaoxin@gmail.com \
    --cc=w@1wt.eu \
    /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;
as well as URLs for NNTP newsgroup(s).