From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: viro@ZenIV.linux.org.uk, weigelt@metux.de, linux-kernel@vger.kernel.org
Subject: Re: VFS + path walktrough
Date: Mon, 05 May 2008 16:16:39 -0400 [thread overview]
Message-ID: <1210018599.7448.1.camel@localhost> (raw)
In-Reply-To: <E1Jt5Td-0006rG-3E@pomaz-ex.szeredi.hu>
On Mon, 2008-05-05 at 20:31 +0200, Miklos Szeredi wrote:
> > > > > Take a look at 9P walk - it does *not* give
> > > > > you anything resembling stat, you just get qids of intermediates.
> > > >
> > > > Which is exactly what's needed to populate the dentry tree, no?
> > >
> > > No - you need inodes as well (i.e. as the absolute least you want
> > > mode and ownership). Which is to say, you need to issue stat on
> > > each component in such situation anyway. Not a win...
>
> And actually even that *could* be a win, if the network latency is
> large. Because by doing the lookup first, the stats can be performed
> in parallel. So a path with an arbitrary number of components could
> be resolved in just 2 RTTs.
...and NFSv4 could do it in a single RPC call (assuming no symlinks or
submounts).
Cheers
Trond
next prev parent reply other threads:[~2008-05-05 20:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 12:40 VFS + path walktrough Enrico Weigelt
2008-05-05 13:06 ` Enrico Weigelt
2008-05-05 13:13 ` Al Viro
2008-05-05 13:43 ` Enrico Weigelt
2008-05-05 15:35 ` Al Viro
2008-05-05 16:43 ` Miklos Szeredi
2008-05-05 17:03 ` Miklos Szeredi
2008-05-05 17:14 ` Al Viro
2008-05-05 17:33 ` Miklos Szeredi
2008-05-05 17:40 ` Al Viro
2008-05-05 18:03 ` Miklos Szeredi
2008-05-05 18:31 ` Miklos Szeredi
2008-05-05 20:16 ` Trond Myklebust [this message]
2008-05-05 20:35 ` Miklos Szeredi
2008-05-05 18:50 ` Enrico Weigelt
2008-05-05 18:23 ` Enrico Weigelt
2008-05-05 18:34 ` Al Viro
2008-05-05 19:02 ` Enrico Weigelt
2008-05-05 19:09 ` Al Viro
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=1210018599.7448.1.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
--cc=weigelt@metux.de \
/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.