From: Al Viro <viro@ftp.linux.org.uk>
To: Christopher Friesen <cfriesen@nortel.com>
Cc: Roland Dreier <rolandd@cisco.com>,
dipankar@in.ibm.com, Sonny Rao <sonny@burdell.org>,
linux-kernel@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>,
bharata@in.ibm.com, trond.myklebust@fys.uio.no
Subject: Re: dentry_cache using up all my zone normal memory -- also seen on 2.6.14-rc2
Date: Thu, 22 Sep 2005 05:17:33 +0100 [thread overview]
Message-ID: <20050922041733.GF7992@ftp.linux.org.uk> (raw)
In-Reply-To: <43322AE6.1080408@nortel.com>
On Wed, Sep 21, 2005 at 09:54:14PM -0600, Christopher Friesen wrote:
> Al Viro wrote:
>
> >>Hmm... could there be a race in shmem_rename()??
>
> >Not likely - in that setup all calls of ->unlink() and ->rename()
> >are completely serialized by ->i_sem on parent. One question:
> >is it dcache or icache that ends up leaking?
>
> dcache. Here's some information I sent to dipankar earlier, with his
> debug patch applied. This is within half a second of the oom killer
> kicking in.
Umm... How many RCU callbacks are pending? Since past the OOM you get
the sucker back to normal... Sounds like you've got a bunch of dentries
on their way to be freed, but the thing that should've been doing final
kmem_cache_free() is getting postponed too much.
next prev parent reply other threads:[~2005-09-22 4:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 16:26 dentry_cache using up all my zone normal memory Christopher Friesen
2005-09-21 16:53 ` Christopher Friesen
2005-09-21 19:46 ` dentry_cache using up all my zone normal memory -- also seen on 2.6.14-rc2 Christopher Friesen
2005-09-21 20:07 ` Sonny Rao
2005-09-21 20:27 ` Christopher Friesen
2005-09-21 20:49 ` Christopher Friesen
2005-09-21 20:59 ` Christopher Friesen
2005-09-21 20:58 ` Sonny Rao
2005-09-21 21:00 ` Dipankar Sarma
2005-09-21 21:14 ` Al Viro
2005-09-21 21:14 ` Trond Myklebust
2005-09-21 21:25 ` Christopher Friesen
2005-09-21 21:29 ` Christopher Friesen
2005-09-21 21:25 ` Christopher Friesen
2005-09-21 22:03 ` Roland Dreier
2005-09-22 3:11 ` Al Viro
2005-09-22 3:54 ` Christopher Friesen
2005-09-22 4:17 ` Al Viro [this message]
2005-09-22 14:47 ` Christopher Friesen
2005-09-22 15:16 ` Christopher Friesen
2005-09-22 18:12 ` dentry_cache using up all my zone normal memory -- new data point Christopher Friesen
2005-09-22 18:27 ` dentry_cache using up all my zone normal memory -- also seen on 2.6.14-rc2 Dipankar Sarma
2005-09-22 19:03 ` Christopher Friesen
2005-09-22 19:18 ` Dipankar Sarma
2005-09-22 21:37 ` Christopher Friesen
2005-09-22 21:44 ` Sonny Rao
2005-09-22 21:55 ` Christopher Friesen
2005-09-22 22:04 ` Randy.Dunlap
2005-09-26 4:43 ` [PATCH/RFC] sysrq: updating console_loglevel Randy.Dunlap
2005-09-22 22:05 ` dentry_cache using up all my zone normal memory -- also seen on 2.6.14-rc2 Christopher Friesen
2005-10-04 19:43 ` Dipankar Sarma
2005-10-04 20:02 ` Christopher Friesen
2005-10-05 4:00 ` Dipankar Sarma
2005-09-30 22:03 ` dentry_cache using up all my zone normal memory Christopher Friesen
2005-10-01 23:22 ` Marcelo
2005-10-02 6:04 ` Christopher Friesen
2005-10-02 19:55 ` Marcelo
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=20050922041733.GF7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=bharata@in.ibm.com \
--cc=cfriesen@nortel.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rolandd@cisco.com \
--cc=sonny@burdell.org \
--cc=trond.myklebust@fys.uio.no \
--cc=tytso@mit.edu \
/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