From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ian Kent <raven@themaw.net>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Use of nameidata in 2.6
Date: 25 Nov 2003 19:03:48 -0500 [thread overview]
Message-ID: <shsad6kvvvf.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.33.0311222037170.770-100000@wombat.indigo.net.au>
>>>>> " " == Ian Kent <raven@themaw.net> writes:
> Any comments on the intended use and what it should contain
> during differnt function calls would be welcome.
The nameidata+intents are there in order to provide hints to
filesystems like NFS and Lustre as to what is the ultimate purpose of
the call to lookup(). This allows the filesystem to perform
optimizations in certain cases.
It also will tell NFSv4 when to use the OPEN call rather than LOOKUP
on the wire (patches not yet merged).
I suggest you treat the nameidata as a read-only structure in this
case unless you are planning on bypassing the VFS and calling the
newly mounted filesystem directly (but why would you want to do that?).
Cheers,
Trond
next prev parent reply other threads:[~2003-11-26 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 12:43 Use of nameidata in 2.6 Ian Kent
2003-11-26 0:03 ` Trond Myklebust [this message]
2003-11-26 1:12 ` Ian Kent
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=shsad6kvvvf.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-fsdevel@vger.kernel.org \
--cc=raven@themaw.net \
/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.