From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: linux-kernel@vger.kernel.org
Subject: Monster file_lock_cache entry in /proc/slabinfo
Date: 15 Sep 2003 16:27:25 -0400 [thread overview]
Message-ID: <m3k78923wy.fsf@lugabout.jhcloos.org> (raw)
My notebook has been slowing down the longer it is up for several
kernel versions. Disk i/o seems to be the chokepoint.
I grabbed slabinfo before today's reboot. The box had been up for 10
days -- it starts to become painful after about five or six days.
The file_lock_cache entry seemed rather engrossed:
file_lock_cache 2339148 2339148 92 42 1 : \
tunables 120 60 0 : \
slabdata 55694 55694 0
55694 slabs containing 2339148 objs?
The biggest user of file locking would be incoming email. uucico(8)
polls a remote server, injects the mail to postfix(8) via postfix's
/usr/sbin/sendmail. Postfix delivers via procmail(1), which pipes
the mail through SpamAssassin and then delivers to foo/. style
destinations. The recipies all start with :0:, so a local lock
file is used in each directory. The destination filesystem is
ext3 with htree (and the default journal style).
I presume something is calling locks_alloc_lock but then failing to
also call locks_free_lock, but /proc/locks only ever shows around 6 or
so entries....
Any suggestions on debugging this?
-JimC
next reply other threads:[~2003-09-15 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 20:27 James H. Cloos Jr. [this message]
2003-09-15 20:25 ` Andrew Morton
2003-09-15 20:59 ` Martin Josefsson
2003-09-15 20:42 ` Chris Wright
2003-09-15 20:56 ` James H. Cloos Jr.
2003-09-15 21:05 ` Martin Josefsson
2003-09-15 21:10 ` Chris Wright
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=m3k78923wy.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--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
all inboxes | Powered by JetHome®