From: Greg Banks <gnb@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: nfs@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [NFS] [PATH 18/19] exportfs: update documentation
Date: Sat, 15 Sep 2007 01:24:24 +1000 [thread overview]
Message-ID: <20070914152424.GJ21965@sgi.com> (raw)
In-Reply-To: <20070830131724.GS6834@lst.de>
On Thu, Aug 30, 2007 at 03:17:24PM +0200, Christoph Hellwig wrote:
> + encode_fh (optinonal)
^^^^^^^^^
> + Takes a dentry and creates a filehandle fragment which can later be used
> + to find/create a dentry for the same object. The default implementation
> + creates a filehandle fragment that encodes a 32bit inode and generation
> + number for the inode encoded, and if nessecary the same information for
^^^^^^^^^
> + the parent.
> +
> + fh_to_dentry (mandatory)
> + Given a filehandle fragment, this should find the implied object and
> + create a dentry for it (possibly with d_alloc_anon).
> +
> + fh_to_parent (optional but strongly recommended)
> + Given a filehandle fragment, this should find the parent of the
> + implied object and create a dentry for it (possibly with d_alloc_anon).
> + May simplify fail if the filehandle fragment is too small.
^^^^^^^^
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
next prev parent reply other threads:[~2007-09-14 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 13:17 [PATH 18/19] exportfs: update documentation Christoph Hellwig
2007-08-30 13:17 ` Christoph Hellwig
2007-09-14 15:24 ` Greg Banks [this message]
2007-09-14 16:03 ` [PATCH] exportfs: fix doc types Christoph Hellwig
2007-09-14 16:40 ` J. Bruce Fields
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=20070914152424.GJ21965@sgi.com \
--to=gnb@sgi.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfs@lists.sourceforge.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.