From: Andreas Dilger <adilger@clusterfs.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/16] GFS2: File and inode operations
Date: Mon, 24 Apr 2006 16:19:57 -0600 [thread overview]
Message-ID: <20060424221957.GW6075@schatzie.adilger.int> (raw)
In-Reply-To: <1145886796.3856.161.camel@quoit.chygwyn.com>
On Apr 24, 2006 14:53 +0100, Steven Whitehouse wrote:
> On Sun, 2006-04-23 at 01:55 -0600, Andreas Dilger wrote:
> > > +++ b/include/linux/iflags.h
> > > @@ -0,0 +1,104 @@
> > > +#define IFLAG_TOPDIR __IFL(TopDir) /* 0x00020000 */
> > > +#define IFLAG_DIRECTIO __IFL(DirectIO) /* 0x00040000 */
> > > +#define IFLAG_INHERITDIRECTIO __IFL(InheritDirectIO) /* 0x00080000 */
> > > +#define IFLAG_INHERITJDATA __IFL(InheritJdata) /* 0x00100000 */
> > > +#define IFLAG_RESERVED __IFL(Reserved) /* 0x80000000 */
> >
> > Actually, the 0x0080000 flag has been reserved by e2fsprogs for ext3
> > extents for a while already. AFAICS, there are no other flags in the
> > current e2fsprogs that aren't listed above.
>
> So if I call that one IFLAG_EXTENT, then I presume that will be ok?
> What about the 0x00040000 flag? That would seem to be a gap in the
> sequence (ignoring GFS flags for now), so should I leave that reserved
> for use by ext2/3 as well?
To be honest, I don't know if 0x40000 is used or not. It isn't in the
e2fsprogs version of ext2_fs.h.
> > The other tidbit is that new ext2/ext3 files generally inherit the flags
> > from their parent directory, so it isn't clear if there is really a need
> > for a distinction between DIRECTIO and INHERIT_DIRECTIO, and similarly
> > JDATA and INHERIT_JDATA? Generally, I'd think that JDATA isn't meaningful
> > on directories (since they are metadata and journaled anyways), nor is
> > DIRECTIO so their only meaning on a directory is "INHERIT for new files".
>
> Yes, that sounds like a good plan. The only downside (purely from a GFS2
> point of view, it won't affect anybody else) means that its no longer a
> 1:1 relationship between flags, so in order to do the conversion, I'd
> have to use something a little more elaborate than the inline function I
> added to the iflags.h header file,
Hmm, maybe I don't understand the GFS2 issue then? Why not just use
IFLAG_JDATA on the directory and remove the use of IFLAG_INHERITJDATA
(equivalent) entirely from GFS2? Does the implementation depend on a
distinction between these on a directory?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-04-24 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 16:13 [PATCH 05/16] GFS2: File and inode operations Steven Whitehouse
2006-04-23 7:55 ` Andreas Dilger
2006-04-24 13:53 ` Steven Whitehouse
2006-04-24 22:19 ` Andreas Dilger [this message]
2006-04-25 9:27 ` Steven Whitehouse
2006-04-25 10:26 ` Christoph Hellwig
2006-04-25 11:14 ` Steven Whitehouse
2006-04-25 12:38 ` 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=20060424221957.GW6075@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
/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).