From: Martin Josefsson <gandalf@wlug.westbo.se>
To: "James H. Cloos Jr." <cloos@jhcloos.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Chris Wright <chrisw@osdl.org>
Subject: Re: Monster file_lock_cache entry in /proc/slabinfo
Date: Mon, 15 Sep 2003 23:05:05 +0200 [thread overview]
Message-ID: <1063659904.2500.4.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <m38yop22jt.fsf@lugabout.jhcloos.org>
On Mon, 2003-09-15 at 22:56, James H. Cloos Jr. wrote:
> Is file_lock_cache only a recent issue, then? The slowdown has been
> going on for at least the last 20 or so release tags.
>
> If this is new I probably need to look at htree or the possibility
> that it is a disk firmware issue (it being a laptop and all)....
This has been with us for some time, it just got fixed :)
--
/Martin
next prev parent reply other threads:[~2003-09-15 21:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 20:27 James H. Cloos Jr.
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 [this message]
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=1063659904.2500.4.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=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®