From: Chris Wright <chrisw@osdl.org>
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 14:10:27 -0700 [thread overview]
Message-ID: <20030915141027.G1363@osdlab.pdx.osdl.net> (raw)
In-Reply-To: <m38yop22jt.fsf@lugabout.jhcloos.org>; from cloos@jhcloos.com on Mon, Sep 15, 2003 at 04:56:54PM -0400
* James H. Cloos Jr. (cloos@jhcloos.com) 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.
Comparing the patch lines to the repo history in bk, this looks like
it's been around since 2.5.39 or so...I suspect this patch is all you
need.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2003-09-15 21:10 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
2003-09-15 21:10 ` Chris Wright [this message]
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=20030915141027.G1363@osdlab.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@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®