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 17:21:30 +0800 [thread overview]
Message-ID: <4B41B31A.8030307@oracle.com> (raw)
In-Reply-To: <20100104085806.GA13852@mail.oracle.com>
Joel Becker wrote:
> On Mon, Jan 04, 2010 at 10:36:15AM +0800, tristan wrote:
>
>> 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?
>>
>
> No, I don't mean that. I mean we have ocfs2_fs.h and
> ocfs2_ioctl.h in both the kernel and the tools.
>
>
>> If not, why we need maintain two ioctl headers in kernel part(ioctl.h and ocfs2_ioctl.h)?
>>
>
> ioctl.h contains things that are only important inside the
> kernel build; specifically, the declarations of the ioctl functions
> called by file_operations. No userspace program needs the declaration
> of kernel code functions. ocfs2_ioctl.h should contain the things a
> userspace program needs to invoke the ioctls. The IOC definitions and
> any structures they use.
> Basically, anything ocfs2_*.h is a userspace header that can be
> installed for userspace programs to use. They get copied to ocfs2-tools
> include/ocfs2-kernel. All the other headers are kernel-only.
>
Oh, I got the naming convention of "ocfs2_*.h":-)
Thanks for the clarification!
> Joel
>
>
>
prev parent reply other threads:[~2010-01-04 9:21 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
2010-01-04 8:58 ` Joel Becker
2010-01-04 9:21 ` tristan [this message]
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=4B41B31A.8030307@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.