From: Paul Menage <pmenage@ensim.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
lse-tech <lse-tech@lists.sourceforge.net>
Cc: pmenage@ensim.com
Subject: Re: [Lse-tech] Re: [RFC] dcache scalability patch (2.4.17)
Date: Sat, 13 Jul 2002 10:51:10 -0700 [thread overview]
Message-ID: <E17TR30-0006Yu-00@pmenage-dt.ensim.com> (raw)
In-Reply-To: Your message of "Sat, 13 Jul 2002 13:33:10 EDT." <Pine.GSO.4.21.0207131328360.15574-100000@weyl.math.psu.edu>
>
>
>On Sat, 13 Jul 2002, Paul Menage wrote:
>
>> - accessing foo/../bar, won't mark foo as referenced, even though it
>> might be being referenced frequently. Probably not a common case for foo
>> to be accessed exclusively in this way, but it could be fixed by marking
>> a dentry referenced when following ".."
>
>It certainly will. Look - until ->d_count hits zero referenced bit is
>not touched or looked at. At all.
>
>Look at the code. There is _no_ aging for dentries with positive ->d_count.
>They start aging only when after they enter unused_list...
>
Yes, but with the fastwalk lookup, accessing foo/../bar won't do a
dget() for foo (assuming it was cached), and hence will never do a
dput() on it either. So if the only references to foo are as foo/../bar
then its d_count will stay zero and it will never be marked referenced.
(Or am I missing something?)
Paul
next prev parent reply other threads:[~2002-07-13 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 14:09 Maneesh Soni
2002-07-12 14:13 ` [Lse-tech] " Christoph Hellwig
2002-07-12 16:20 ` Dipankar Sarma
2002-07-15 8:10 ` Maneesh Soni
2002-07-15 8:25 ` Maneesh Soni
2002-07-12 14:29 ` Alexander Viro
2002-07-12 16:10 ` [Lse-tech] " Dipankar Sarma
2002-07-12 18:02 ` Dipankar Sarma
2002-07-12 18:10 ` Hanna Linder
2002-07-12 17:35 ` Paul Menage
2002-07-13 8:52 ` Alexander Viro
2002-07-13 17:25 ` Paul Menage
2002-07-13 17:33 ` Alexander Viro
2002-07-13 17:51 ` Paul Menage [this message]
2002-07-13 17:54 ` Alexander Viro
2002-07-15 0:10 ` Linus Torvalds
2002-07-12 22:50 ` Hanna Linder
2002-07-15 7:49 ` Maneesh Soni
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=E17TR30-0006Yu-00@pmenage-dt.ensim.com \
--to=pmenage@ensim.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=viro@math.psu.edu \
/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®