From: "Xin Zhao" <uszhaoxin@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: What's the NFS OOM problem?
Date: Tue, 8 Aug 2006 18:24:47 -0400 [thread overview]
Message-ID: <4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com> (raw)
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.
Can someone help me and give me a brief description on OOM issue?
Many many thanks!
-x
next reply other threads:[~2006-08-08 22:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 22:24 Xin Zhao [this message]
2006-08-09 2:33 ` What's the NFS OOM problem? 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
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=4ae3c140608081524u4666fb7x741734908c35cfe6@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).