From: tristan <tristan.ye@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add stuffs associated with ocfs2_info_request ioctls to ioctl.h
Date: Mon, 04 Jan 2010 10:36:15 +0800 [thread overview]
Message-ID: <4B41541F.8030704@oracle.com> (raw)
In-Reply-To: <20091231201059.GB3301@mail.oracle.com>
Joel Becker wrote:
> On Thu, Dec 31, 2009 at 04:18:43PM +0800, Tristan Ye wrote:
>
>> Currently we were adding ioctl cmds/structures for ocfs2 into ocfs2_fs.h
>> which was used for define ocfs2 on-disk layout. That sounds a little bit
>> confusing, and it can be quickly polluted espcially when growing the
>> ocfs2_info_request ioctls afterwards. The appropriate place to kept in-memory
>> ioctl structures is ioctl.h I guess.
>>
>
> We want a separate ocfs2_ioctl.h. The definitions of the ioctl
> and its structures are things a userspace program would want to use.
> ioctl.h, on the other hand, is an internal header for libocfs2.
>
Oh, I may misunderstand your words, Joel. Did you mean we only split the on-disk layout and ioctls into two parts(ocfs2_fs.h and ocfs2_ioctl.h) in ocfs2-tools for userspace,
while kernel part still maintains one ocfs2_fs.h to cover both definitions for on-disk and ioctl strutures?
If so, why don't we keep a unification in ocfs2-tools and kernel part?
If not, why we need maintain two ioctl headers in kernel part(ioctl.h and ocfs2_ioctl.h)?
Tristan.
> Joel
>
>
next prev parent reply other threads:[~2010-01-04 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 8:18 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add stuffs associated with ocfs2_info_request ioctls to ioctl.h Tristan Ye
2009-12-31 8:18 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Add new OCFS2_INFO_IOC ioctls for ocfs2 v4 Tristan Ye
2009-12-31 20:13 ` Joel Becker
2009-12-31 20:10 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add stuffs associated with ocfs2_info_request ioctls to ioctl.h Joel Becker
2010-01-04 2:36 ` tristan [this message]
2010-01-04 8:58 ` Joel Becker
2010-01-04 9:21 ` tristan
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=4B41541F.8030704@oracle.com \
--to=tristan.ye@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.