From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: nfs@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: [NFS] [PATCH 2/18] exportfs: add fid type
Date: Wed, 28 Mar 2007 19:35:20 -0400 [thread overview]
Message-ID: <20070328233520.GL21221@fieldses.org> (raw)
In-Reply-To: <20070317011009.GC24947@infradead.org>
On Sat, Mar 17, 2007 at 01:10:09AM +0000, Christoph Hellwig wrote:
> Add a structured fid type so that we don't have to pass an array
> of u32 values around everywhere. It's a union of possible layouts.
> As a start there's only the u32 array and the traditional 32bit
> inode format, but there will be more in one of my next patchset
> when I start to document the various filehandle formats we have
> in lowlevel filesystems better.
>
> Also add an enum that gives the various filehandle types humand
> readable names.
>
> Note: Some people might think the struct containing an anonymous
> union is ugly, but I didn't want to pass around a raw union type.
A basic question: what do these apply against? For example, I don't
have this file:
> Index: linux-2.6/include/linux/exportfs.h
> ===================================================================
> --- linux-2.6.orig/include/linux/exportfs.h 2007-03-16 15:44:02.000000000 +0100
> +++ linux-2.6/include/linux/exportfs.h 2007-03-16 15:44:09.000000000 +0100
--b.
next prev parent reply other threads:[~2007-03-28 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 1:10 [PATCH 2/18] exportfs: add fid type Christoph Hellwig
2007-03-28 23:35 ` J. Bruce Fields [this message]
2007-03-29 9:28 ` Christoph Hellwig
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=20070328233520.GL21221@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).