From: Linus Torvalds <torvalds@transmeta.com>
To: bristuccia@starentnetworks.com, linux-kernel@vger.kernel.org
Subject: Re: repeated failed open()'s results in lots of used memory [Was: [Fwd: memory consumption]]
Date: Wed, 1 Aug 2001 15:54:04 -0700 [thread overview]
Message-ID: <200108012254.f71Ms4W14080@penguin.transmeta.com> (raw)
In-Reply-To: <3B686D73.6040602@starentnetworks.com>
In article <3B686D73.6040602@starentnetworks.com> you write:
>
>Note that we increase the default values for certain FS parameters:
>
>echo '16384' >/proc/sys/fs/super-max
>echo '32768' >/proc/sys/fs/file-max
>echo '65535' > /proc/sys/fs/inode-max
Doesn't matter.
The thing that you end up hitting looks very much like just tons of
negative dentries lying around.
If you are even moderately confident about playing around with the
kernel, I would suggest testing the following approach (if you aren't
comforable with playing with the kernel, I hope somebody else is willing
to try this out, or I could try to cook up a patch to test later this
week)
- add a new dentry list in addition to the current 'dentry_unused' list
in linux/fs/dentry.c:
static LIST_HEAD(dentry_unused_negative);
- when 'dput()' adds a dentry to the old 'dentry_unused' list it would
instead check whether the dentry is negative, and if so add it to the
negative list instead:
list = &dentry_unused;
if (!dentry->d_inode)
list = &dentry_unused_negative;
list_add(&dentry->d_lru, list);
- add a new "shrink_negative_dentries()" function that just does
something like
struct list_head *tmp;
spin_lock(&dcache_lock);
for (;;) {
struct list_head * tmp = dentry_unused_negative.next;
if (tmp == &dentry_unused_negative)
break;
struct dentry *dentry = list_entry(tmp, struct dentry, d_lru);
tmp = tmp->next;
if (atomic_read(&dentry->d_count))
BUG();
if (dentry->d_inode)
BUG();
prune_one_dentry(dentry);
/* prune_one_dentry() releases the lock */
spin_lock(&dcache_lock);
}
spin_unlock(&dcache_lock);
- make all the things that shrink dentries (notably the
shrink_dcache_memory() function) call the above function first.
Does that fix the behaviour for you?
Linus
next prev parent reply other threads:[~2001-08-01 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 20:58 Brian Ristuccia
2001-08-01 22:04 ` Andreas Dilger
2001-08-01 22:36 ` Brian Ristuccia
2001-08-01 22:53 ` Andreas Dilger
2001-08-01 23:57 ` Linus Torvalds
2001-08-01 22:54 ` Linus Torvalds [this message]
2001-08-01 23:08 ` Alexander Viro
2001-08-01 23:14 ` Linus Torvalds
2001-08-02 1:23 ` Alexander Viro
2001-08-02 4:42 ` Rik van Riel
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=200108012254.f71Ms4W14080@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=bristuccia@starentnetworks.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®