From: Paul Menage <pmenage@ensim.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org, pmenage@ensim.com
Subject: Re: [PATCH] 2.5.6-pre3 Fast Walk Dcache
Date: Fri, 08 Mar 2002 13:28:23 -0800 [thread overview]
Message-ID: <E16jRuZ-00076W-00@pmenage-dt.ensim.com> (raw)
In-Reply-To: <0C01A29FBAE24448A792F5C68F5EA47D2260CB@nasdaq.ms.ensim.com>
In article <0C01A29FBAE24448A792F5C68F5EA47D2260CB@nasdaq.ms.ensim.com>,
you write:
>
>Changed path_lookup to hold the dcache_lock instead of incrementing the
>d_count reference counter while walking the path as long as the desired
>dentry's are found in the dcache. Dave Olien wrote permission_exec_lite.
>These ideas came from Al Viro to decrease cacheline bouncing.
Some points:
1) You're missing parentheses in cached_lookup_nd() and path_lookup():
if(!nd->flags & LOOKUP_LOCKED)
return cached_lookup(nd->dentry, name, flags);
...
if (!nd->flags & LOOKUP_LOCKED)
dput(nd->dentry);
! binds closer than binary &, so the tests will never be true (and gcc
probably optimises the entire tests/calls away).
2) Since cached_lookup_nd() calls __d_lookup() and hence
__dget_locked(), it's not clear how you actually avoid incrementing the
d_count values of the dentries, other than the root/cwd dentries. Can
you explain the logic in a little more detail?
e.g. if you do path_lookup("/usr/bin", 0, nd), this translates into
(substituting names for dentries for readability ...)
path_walk("/usr/bin", nd)
cached_lookup("/", "usr", LOOKUP_CONTINUE)
__d_lookup("/", "usr")
__dget_locked("/usr")
atomic_inc(&"/usr"->d_count)
3) If you replace walk_init_root() and path_lookup() with something
like the following, you can pull the ugliness of walk_init_root() out
of path_lookup(). Basically, make walk_init_root() recognise
LOOKUP_LOCKED and take the dcache_lock rather than grabbing refcounts.
walk_init_root() drops the LOOKUP_LOCKED flag if necessary while
calling __emul_lookup_dentry() to avoid additional complexity. If
walk_init_root() returns 0, then the dcache lock wasn't taken,
regardless of whether the nd.flags had LOOKUP_LOCKED set.
static inline int
walk_init_root(const char *name, struct nameidata *nd)
{
unsigned int flags = nd->flags;
read_lock(¤t->fs->lock);
if (current->fs->altroot && !(nd->flags & LOOKUP_NOALT)) {
if(flags & LOOKUP_LOCKED)
nd->flags &= ~LOOKUP_LOCKED;
nd->mnt = mntget(current->fs->altrootmnt);
nd->dentry = dget(current->fs->altroot);
read_unlock(¤t->fs->lock);
if (__emul_lookup_dentry(name,nd))
return 0;
if(flags & LOOKUP_LOCKED)
nd->flags = flags;
read_lock(¤t->fs->lock);
}
nd->mnt = current->fs->rootmnt;
nd->dentry = current->fs->root;
if(flags & LOOKUP_LOCKED) {
read_lock(&dcache_lock);
} else {
mntget(nd->mnt);
dget(nd->dentry);
}
read_unlock(¤t->fs->lock);
return 1;
}
...
int path_lookup(const char *name, unsigned int flags, struct nameidata
*nd)
{
nd->last_type = LAST_ROOT; /* if there are only slashes... */
nd->flags = flags | LOOKUP_LOCKED;
if (*name=='/'){
if(!walk_init_root(name, nd))
return 0;
} else{
read_lock(¤t->fs->lock);
spin_lock(&dcache_lock);
nd->mnt = current->fs->pwdmnt;
nd->dentry = current->fs->pwd;
read_unlock(¤t->fs->lock);
}
return (path_walk(name, nd));
}
Paul
next parent reply other threads:[~2002-03-08 21:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0C01A29FBAE24448A792F5C68F5EA47D2260CB@nasdaq.ms.ensim.com>
2002-03-08 21:28 ` Paul Menage [this message]
2002-03-09 1:30 ` Hanna Linder
2002-03-09 2:03 ` [PATCH] 2.5.6 Fast Walk Dcache (improved) Paul Menage
2002-03-09 2:59 ` Paul Menage
2002-03-10 19:51 ` Hanna V Linder
2002-03-11 7:13 ` Paul Menage
2002-03-12 7:16 ` Paul Menage
2002-03-08 0:25 [PATCH] 2.5.6-pre3 Fast Walk Dcache Hanna Linder
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=E16jRuZ-00076W-00@pmenage-dt.ensim.com \
--to=pmenage@ensim.com \
--cc=hannal@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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®