From: Greg KH <greg@kroah.com>
To: Joel Fuster <j@fuster.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysfs_dir_cache growing out of control
Date: Thu, 23 Aug 2007 17:54:29 -0700 [thread overview]
Message-ID: <20070824005429.GA32265@kroah.com> (raw)
In-Reply-To: <46CE29DA.60409@fuster.org>
On Thu, Aug 23, 2007 at 08:44:10PM -0400, Joel Fuster wrote:
> Greg KH wrote:
>> On Wed, Aug 22, 2007 at 11:56:44PM -0400, Joel Fuster wrote:
>>> Joel Fuster wrote:
>>>> Hi,
>>>> I am running 2.6.22.3. For reasons that escape me, over time (days) the
>>>> sysfs_dir_cache, dentry, and inode_cache SLUB entries grow until they
>>>> consume all the memory on my system, requiring a reboot.
>> Hm, those items should consume all the memory, but it should be freed if
>> you have memory pressure from other places. Does it cause the machine
>> to lock up, or you just got scared when seeing them?
> Right. The problem is that the memory never seems to get freed no matter
> what I do. I've tried setting /proc/sys/vm/vfs_cache_pressure to 10000,
> but after a few days all my programs are running out of swap and I have to
> reboot to get things back to a usable state.
>
>> Oh, and does the same thing happen if you do not use SLUB, but rather
>> the older SLAB?
>
> OK I just rebuilt 2.6.22.3 with SLAB and I seem to be getting the same
> result..obviously I haven't waited several days, but
> sysfs_dir_cache/dentry/inode_cache grow continuously when scanbuttond is
> running, and stop growing when it isn't.
Do you have a pointer to the scanbuttond source code? I'll try to take
a look at this tomorrow.
thanks,
greg k-h
next prev parent reply other threads:[~2007-08-24 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 0:25 sysfs_dir_cache growing out of control Joel Fuster
2007-08-23 3:56 ` Joel Fuster
2007-08-23 9:59 ` Greg KH
2007-08-24 0:44 ` Joel Fuster
2007-08-24 0:54 ` Greg KH [this message]
2007-08-24 1:26 ` Gabriel C
2007-09-05 16:03 ` Andrew Morton
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=20070824005429.GA32265@kroah.com \
--to=greg@kroah.com \
--cc=j@fuster.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