linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Btrfs Development List <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 6/8] btrfs: uapi/linux/btrfs.h migration, move struct btrfs_ioctl_defrag_range_args
Date: Wed, 27 Apr 2016 14:10:29 -0700	[thread overview]
Message-ID: <20160427211029.GI15822@localhost.localdomain> (raw)
In-Reply-To: <1459541670-4097-7-git-send-email-jeffm@suse.com>

On Fri, Apr 01, 2016 at 04:14:28PM -0400, Jeff Mahoney wrote:
> struct btrfs_ioctl_defrag_range_args is used by the BTRFS_IOC_DEFRAG_RANGE
> ioctl.

Reviewed-by: Liu Bo <bo.li.liu@oracle.com>

Thanks,

-liubo
> 
> Signed-off-by: Jeff Mahoney <jeffm@suse.com>
> ---
>  fs/btrfs/ctree.h           | 31 -------------------------------
>  include/uapi/linux/btrfs.h | 38 +++++++++++++++++++++++++++++++++++++-
>  2 files changed, 37 insertions(+), 32 deletions(-)
> 
> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
> index 378482c..89f36b6 100644
> --- a/fs/btrfs/ctree.h
> +++ b/fs/btrfs/ctree.h
> @@ -1992,37 +1992,6 @@ struct btrfs_root {
>  	atomic_t qgroup_meta_rsv;
>  };
>  
> -struct btrfs_ioctl_defrag_range_args {
> -	/* start of the defrag operation */
> -	__u64 start;
> -
> -	/* number of bytes to defrag, use (u64)-1 to say all */
> -	__u64 len;
> -
> -	/*
> -	 * flags for the operation, which can include turning
> -	 * on compression for this one defrag
> -	 */
> -	__u64 flags;
> -
> -	/*
> -	 * any extent bigger than this will be considered
> -	 * already defragged.  Use 0 to take the kernel default
> -	 * Use 1 to say every single extent must be rewritten
> -	 */
> -	__u32 extent_thresh;
> -
> -	/*
> -	 * which compression method to use if turning on compression
> -	 * for this defrag operation.  If unspecified, zlib will
> -	 * be used
> -	 */
> -	__u32 compress_type;
> -
> -	/* spare for later */
> -	__u32 unused[4];
> -};
> -
>  
>  /*
>   * inode items have the data typically returned from stat and store other
> diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
> index abae362..98aff38 100644
> --- a/include/uapi/linux/btrfs.h
> +++ b/include/uapi/linux/btrfs.h
> @@ -474,9 +474,45 @@ struct btrfs_ioctl_clone_range_args {
>    __u64 dest_offset;
>  };
>  
> -/* flags for the defrag range ioctl */
> +/*
> + * flags definition for the defrag range ioctl
> + *
> + * Used by:
> + * struct btrfs_ioctl_defrag_range_args.flags
> + */
>  #define BTRFS_DEFRAG_RANGE_COMPRESS 1
>  #define BTRFS_DEFRAG_RANGE_START_IO 2
> +struct btrfs_ioctl_defrag_range_args {
> +	/* start of the defrag operation */
> +	__u64 start;
> +
> +	/* number of bytes to defrag, use (u64)-1 to say all */
> +	__u64 len;
> +
> +	/*
> +	 * flags for the operation, which can include turning
> +	 * on compression for this one defrag
> +	 */
> +	__u64 flags;
> +
> +	/*
> +	 * any extent bigger than this will be considered
> +	 * already defragged.  Use 0 to take the kernel default
> +	 * Use 1 to say every single extent must be rewritten
> +	 */
> +	__u32 extent_thresh;
> +
> +	/*
> +	 * which compression method to use if turning on compression
> +	 * for this defrag operation.  If unspecified, zlib will
> +	 * be used
> +	 */
> +	__u32 compress_type;
> +
> +	/* spare for later */
> +	__u32 unused[4];
> +};
> +
>  
>  #define BTRFS_SAME_DATA_DIFFERS	1
>  /* For extent-same ioctl */
> -- 
> 2.7.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-04-27 21:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 20:14 [PATCH 0/8] btrfs: uapi migration for user-visible API components Jeff Mahoney
2016-04-01 20:14 ` [PATCH 1/8] btrfs: uapi/linux/btrfs.h migration, move BTRFS_LABEL_SIZE Jeff Mahoney
2016-04-27 19:23   ` Liu Bo
2016-04-01 20:14 ` [PATCH 2/8] btrfs: uapi/linux/btrfs.h migration, qgroup limit flags Jeff Mahoney
2016-04-27 19:24   ` Liu Bo
2016-04-01 20:14 ` [PATCH 3/8] btrfs: uapi/linux/btrfs.h migration, document subvol flags Jeff Mahoney
2016-04-27 20:27   ` Liu Bo
2016-04-01 20:14 ` [PATCH 4/8] btrfs: uapi/linux/btrfs.h migration, move feature flags Jeff Mahoney
2016-04-27 21:08   ` Liu Bo
2016-04-01 20:14 ` [PATCH 5/8] btrfs: uapi/linux/btrfs.h migration, move balance flags Jeff Mahoney
2016-04-27 21:09   ` Liu Bo
2016-04-01 20:14 ` [PATCH 6/8] btrfs: uapi/linux/btrfs.h migration, move struct btrfs_ioctl_defrag_range_args Jeff Mahoney
2016-04-27 21:10   ` Liu Bo [this message]
2016-04-01 20:14 ` [PATCH 7/8] btrfs: uapi/linux/btrfs_tree.h migration, item types and defines Jeff Mahoney
2016-04-27 21:12   ` Liu Bo
2016-04-01 20:14 ` [PATCH 8/8] btrfs: uapi/linux/btrfs_tree.h, use __u8 and __u64 Jeff Mahoney
2016-04-27 21:12   ` Liu Bo
2016-04-27 19:37 ` [PATCH 0/8] btrfs: uapi migration for user-visible API components Josef Bacik
2016-04-27 22:42 ` David Sterba

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=20160427211029.GI15822@localhost.localdomain \
    --to=bo.li.liu@oracle.com \
    --cc=jeffm@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).