public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	ocfs2-devel@oss.oracle.com, sunil.mushran@oracle.com
Subject: Re: [PATCH] fs: add FS_IOC_UNRESVSP/FS_IOC_UNRESVSP64 ioctls
Date: Wed, 21 Sep 2011 08:46:55 +1000	[thread overview]
Message-ID: <20110920224655.GJ15688@dastard> (raw)
In-Reply-To: <1316528400-1797-1-git-send-email-dmonakhov@openvz.org>

On Tue, Sep 20, 2011 at 06:20:00PM +0400, Dmitry Monakhov wrote:
> Add ioctl interface for FALLOC_FL_PUNCH_HOLE. Ioctls are synonyms of
> XFS_IOC_UNRESVSP ioctls. Yes probably one can say than we already have
> a syscall intercase for fallocate, and in general this is right but:
>  - We already have FS_IOC_RESVSP (synonym of XFS_IOC_RESVSP)
>    and it heavily used. So actually this ioctl is not a
>    brand new one. It just makes RSV/URSV interface complete.

Those exist because filesystems copied them from XFS before
fallocate() was implemented. They are considered "legacy" interfaces
and are only kept for compatibility with old applications that were
using the XFS interfaces before fallocate came along.

>  - There are miliones lines of userspace code written
>    that can be reused for generic linux filesystems without
>    modification. SGI has open sourced many good stuff which are
>    under rapid development by linux community. For example
>    kernel.org/scm/fs/xfs/xfstests-dev.git  currently is one of
>    most used fs-regression testing suite.

Yes, but as it xfstests is currently maintained, the correct thing
to do is to extend it to use fallocate() interfaces so they get
tested. We've already done this for tools the test suite uses like
fsx, and there are new fallocate based hole punching tests that
have been added recently.

IMO, no new functionality should use [X]FS_IOC_*RESVSP ioctl
interfaces, and code that currently uses them should be ported to
use fallocate.

>    In other words i've added only 30lines of code, and get great
>    many good tools working for me, IMHO it is good deal.

Such as? I can't think of many tools in the linux ecosystem other
than XFS specific utilities that actually support hole
punching through this interface.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2011-09-20 22:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 14:20 [PATCH] fs: add FS_IOC_UNRESVSP/FS_IOC_UNRESVSP64 ioctls Dmitry Monakhov
2011-09-20 22:46 ` Dave Chinner [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=20110920224655.GJ15688@dastard \
    --to=david@fromorbit.com \
    --cc=dmonakhov@openvz.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=sunil.mushran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox