From: Dave Chinner <david@fromorbit.com>
To: Dhruvesh Rathore <adrscube@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/4] xfs: Adding XFS_IOC_FIEMAPFS ioctl for use in xfs_spaceman
Date: Tue, 10 Feb 2015 21:17:52 +1100 [thread overview]
Message-ID: <20150210101752.GB12722@dastard> (raw)
In-Reply-To: <54ca35b7.2786440a.6990.450d@mx.google.com>
On Thu, Jan 29, 2015 at 06:59:22PM +0530, Dhruvesh Rathore wrote:
>
> This patch is concerned with the changes to be done in kernel space code for
> turning FS_IOC_FIEMAPFS present in the earlier version of xfs_spaceman
> into an XFS specific ioctl called XFS_IOC_FIEMAPFS, which uses all existing
> fiemap insfrastructure.
> By introducing XFS_IOC_FIMEAPFS ioctl, it can be seperated from file based
> fiemap commands and allows us to review it and push it as we need, making the
> process much simpler.
>
> ----------------------------------------------------------------------------------------
>
> Signed-off-by: Dhruvesh Rathore <dhruvesh_r@outlook.com>
> Signed-off-by: Amey Ruikar <ameyruikar@yahoo.com>
> Signed-off-by: Somdeep Dey <somdeepdey10@gmail.com>
> ---
> fs/ioctl.c | 3 ++-
> include/linux/fs.h | 6 ++++++
> fs/xfs/xfs_ioctl.c | 55 +++++++++++++
> fs/xfs/xfs_fs.h | 1 +
> 4 files changed, 64 insertions(+), 1 deletion(-)
Ok, so this patch doesn't remove any of the now unused
functionality I added to support the VFS based ioctl.
What I'm going to do with this is combine it with the initial
"introduce FS_IOC_FIEMAP" patch I wrote (including all it's
documentation!) as the first patch of the kernel side patch series
to introduced XFS_IOC_FIEMAPFS.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-02-10 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 13:29 [PATCH 3/4] xfs: Adding XFS_IOC_FIEMAPFS ioctl for use in xfs_spaceman Dhruvesh Rathore
2015-02-10 10:17 ` Dave Chinner [this message]
2015-02-11 16:19 ` Dhruvesh Rathore
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=20150210101752.GB12722@dastard \
--to=david@fromorbit.com \
--cc=adrscube@gmail.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox