From: Greg Banks <gnb@sgi.com>
To: Steve Lord <lord@xfs.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: negative dentry_stat.nr_unused causes aggressive dcache pruning
Date: Thu, 9 Dec 2004 10:01:18 +1100 [thread overview]
Message-ID: <20041208230118.GC4239@sgi.com> (raw)
In-Reply-To: <41B77D54.4080909@xfs.org>
On Wed, Dec 08, 2004 at 04:16:52PM -0600, Steve Lord wrote:
>
> I have seen this stat go negative (just from booting up a multi cpu box),
> and looking at the code, it is manipulated without locking in a number
> of places. I have only seen this in real life on a 2.4 kernel, but 2.6
> also looks vulnerable.
On early 2.6.x, a heavy streaming NFS load was a great way to trigger
this. I haven't seen it happen since
http://linus.bkbits.net:8080/linux-2.5/cset@40b8cf606MV-gl6VpDyWKzzW1jaIJw
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
next prev parent reply other threads:[~2004-12-08 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 22:16 negative dentry_stat.nr_unused causes aggressive dcache pruning Steve Lord
2004-12-08 23:01 ` Greg Banks [this message]
2004-12-09 10:09 ` Andrew Morton
2004-12-09 16:33 ` Steve Lord
2004-12-09 20:54 ` Steve Lord
2004-12-09 21:19 ` Andrew Morton
2004-12-09 21:51 ` Steve Lord
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=20041208230118.GC4239@sgi.com \
--to=gnb@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.