All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: What's the NFS OOM problem?
Date: Thu, 10 Aug 2006 06:57:11 +0200	[thread overview]
Message-ID: <20060810045711.GI8776@1wt.eu> (raw)
In-Reply-To: <4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com>

On Tue, Aug 08, 2006 at 06:24:47PM -0400, Xin Zhao wrote:
> I often heard of the OOM probelm in NFS, but don't know what it is.
> Now I am developing a NFS based system and found my system memory
> (server side) is used too fast. I checked the code but didn't find
> memory leaking. So I suspect I run into OOM issue.

I simply think that you're cache is filling while your clients access
a lot of files. That's expected. You might also get quite a bunch of
dentries cached which will not be accounted for in meminfo. Check
/proc/meminfo for the cache+buffer size, and check /proc/slabinfo for
the number of dentries. The usual way to ensure this is only cache is
to allocate a large amount of memory (let's say all the system RAM
provided that everything can get swapped), then free it. You'll see
a lot of free memory after that.

> Can someone help me and give me a brief description on OOM issue?

I don't know about any OOM issue related to NFS. At most it might happen
on the client (eg: stating firefox from an NFS root) which might not have
enough memory for new network buffers, but I don't even know if it's
possible at all.

Regards,
Willy


  parent reply	other threads:[~2006-08-10  5:14 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 [this message]
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
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=20060810045711.GI8776@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uszhaoxin@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.