From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/8] Update ocfs2_fs.h to contain all necessary quota structures and constants
Date: Wed, 29 Jul 2009 11:19:00 -0700 [thread overview]
Message-ID: <20090729181900.GA5849@mail.oracle.com> (raw)
In-Reply-To: <20090729094256.GA17748@duck.suse.cz>
On Wed, Jul 29, 2009 at 11:42:56AM +0200, Jan Kara wrote:
> > > #define OCFS2_GLOBAL_INFO_OFF (sizeof(struct ocfs2_disk_dqheader))
> > > +#define OCFS2_GLOBAL_TREE_BLK 1
> >
> > I don't see GLOBAL_TREE_BLK in the kernel.
> They are in the generic quota header fs/quota/quota_tree.h defining quota
> file format. For global quota files we use generic quota code which also
> defines some parts of the disk format...
<snip>
> These are the same cases. I can split them into a separate header file if
> you like it better. But from the tools point of view, I felt that keeping
> all disk-format related things in one header makes sence.
ocfs2_fs.h is a shared header, though. It needs to have the
same contents in the tools and in the kernel (at any point where the
feature set is identical, of course). Why can't you just put the
quota_tree.h and quotaio_v2.h headers in include/ocfs2-kernel? This not
only signifies that they aren't ocfs2-specific structures, it allows
them to follow the kernel headers in an easier fashion. We do the same
thing with ocfs1_fs_compat.h, which defines the ocfs header we
deliberately break in ocfs2.
Joel
--
"When choosing between two evils, I always like to try the one
I've never tried before."
- Mae West
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2009-07-29 18:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 17:53 [Ocfs2-devel] [PATCH 0/8] Quota support for ocfs2-tools Jan Kara
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 1/8] Update ocfs2_fs.h to contain all necessary quota structures and constants Jan Kara
2009-07-28 21:45 ` Joel Becker
2009-07-29 9:42 ` Jan Kara
2009-07-29 18:19 ` Joel Becker [this message]
2009-07-30 16:57 ` Jan Kara
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 2/8] Provide ocfs2_cached_inode_extend_allocation() Jan Kara
2009-07-28 21:47 ` Joel Becker
2009-07-29 9:46 ` Jan Kara
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 3/8] Implement quota functions to libocfs2 Jan Kara
2009-07-28 7:55 ` Tao Ma
2009-07-28 8:40 ` Jan Kara
2009-07-28 8:43 ` Tao Ma
2009-07-28 10:08 ` Jan Kara
2009-07-28 22:52 ` Joel Becker
2009-07-29 9:57 ` Jan Kara
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 4/8] Write out quota info changes on ocfs2_close() Jan Kara
2009-07-28 22:53 ` Joel Becker
2009-07-29 9:58 ` Jan Kara
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 5/8] Quota support for fsck.ocfs2 Jan Kara
2009-07-28 23:05 ` Joel Becker
2009-07-29 10:07 ` Jan Kara
2009-07-29 14:28 ` Tao Ma
2009-07-29 18:22 ` Joel Becker
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 6/8] Quota support for mkfs.ocfs2 Jan Kara
2009-07-28 8:11 ` Tao Ma
2009-07-28 8:43 ` Jan Kara
2009-07-28 10:09 ` Jan Kara
2009-07-28 23:07 ` Joel Becker
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 7/8] Add quota support to tunefs.ocfs2 Jan Kara
2009-07-29 1:04 ` Joel Becker
2009-07-27 17:53 ` [Ocfs2-devel] [PATCH 8/8] Change headers to reflect that quota is now fully supported Jan Kara
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=20090729181900.GA5849@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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 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.