From: Randy Dunlap <randy.dunlap@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/20] ceph: ioctls
Date: Tue, 8 Sep 2009 16:05:09 -0700 [thread overview]
Message-ID: <20090908160509.bcf511dc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1252450601-17610-19-git-send-email-sage@newdream.net>
On Tue, 8 Sep 2009 15:56:39 -0700 Sage Weil wrote:
> A few Ceph ioctls for getting and setting file layout (striping)
> parameters.
>
> Signed-off-by: Sage Weil <sage@newdream.net>
> ---
> fs/ceph/ioctl.c | 98 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/ceph/ioctl.h | 20 +++++++++++
> 2 files changed, 118 insertions(+), 0 deletions(-)
> create mode 100644 fs/ceph/ioctl.c
> create mode 100644 fs/ceph/ioctl.h
> diff --git a/fs/ceph/ioctl.h b/fs/ceph/ioctl.h
> new file mode 100644
> index 0000000..56f5e2c
> --- /dev/null
> +++ b/fs/ceph/ioctl.h
> @@ -0,0 +1,20 @@
> +#ifndef FS_CEPH_IOCTL_H
> +#define FS_CEPH_IOCTL_H
> +
> +#include <linux/ioctl.h>
> +#include <linux/types.h>
> +
> +#define CEPH_IOCTL_MAGIC 0x97
> +
> +/* just use u64 to align sanely on all archs */
> +struct ceph_ioctl_layout {
> + __u64 stripe_unit, stripe_count, object_size;
> + __u64 data_pool;
> +};
> +
> +#define CEPH_IOC_GET_LAYOUT _IOR(CEPH_IOCTL_MAGIC, 1, \
> + struct ceph_ioctl_layout)
> +#define CEPH_IOC_SET_LAYOUT _IOW(CEPH_IOCTL_MAGIC, 2, \
> + struct ceph_ioctl_layout)
> +
> +#endif
> --
Please also update Documentation/ioctl/ioctl-number.txt
---
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/
next prev parent reply other threads:[~2009-09-08 23:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 22:56 [PATCH 00/20] ceph distributed file system client Sage Weil
2009-09-08 22:56 ` [PATCH 01/20] ceph: documentation Sage Weil
2009-09-08 22:56 ` [PATCH 02/20] ceph: on-wire types Sage Weil
2009-09-08 22:56 ` [PATCH 03/20] ceph: client types Sage Weil
2009-09-08 22:56 ` [PATCH 04/20] ceph: ref counted buffer Sage Weil
2009-09-08 22:56 ` [PATCH 05/20] ceph: super.c Sage Weil
2009-09-08 22:56 ` [PATCH 06/20] ceph: inode operations Sage Weil
2009-09-08 22:56 ` [PATCH 07/20] ceph: directory operations Sage Weil
2009-09-08 22:56 ` [PATCH 08/20] ceph: file operations Sage Weil
2009-09-08 22:56 ` [PATCH 09/20] ceph: address space operations Sage Weil
2009-09-08 22:56 ` [PATCH 10/20] ceph: MDS client Sage Weil
2009-09-08 22:56 ` [PATCH 11/20] ceph: OSD client Sage Weil
2009-09-08 22:56 ` [PATCH 12/20] ceph: CRUSH mapping algorithm Sage Weil
2009-09-08 22:56 ` [PATCH 13/20] ceph: monitor client Sage Weil
2009-09-08 22:56 ` [PATCH 14/20] ceph: capability management Sage Weil
2009-09-08 22:56 ` [PATCH 15/20] ceph: snapshot management Sage Weil
2009-09-08 22:56 ` [PATCH 16/20] ceph: messenger library Sage Weil
2009-09-08 22:56 ` [PATCH 17/20] ceph: nfs re-export support Sage Weil
2009-09-08 22:56 ` [PATCH 18/20] ceph: ioctls Sage Weil
2009-09-08 22:56 ` [PATCH 19/20] ceph: debugfs Sage Weil
2009-09-08 22:56 ` [PATCH 20/20] ceph: Kconfig, Makefile Sage Weil
2009-09-08 23:05 ` Randy Dunlap [this message]
2009-09-08 23:45 ` [PATCH 18/20] ceph: ioctls Sage Weil
2009-09-08 23:10 ` [PATCH 00/20] ceph distributed file system client Daniel Walker
2009-09-08 23:47 ` Sage Weil
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=20090908160509.bcf511dc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.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 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.