public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Josef Bacik <josef@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: add fpunch command for hole punching via fallocate
Date: Wed, 19 Jan 2011 08:23:03 +1100	[thread overview]
Message-ID: <20110118212303.GV28803@dastard> (raw)
In-Reply-To: <20110118131203.GA4349@infradead.org>

On Tue, Jan 18, 2011 at 08:12:03AM -0500, Christoph Hellwig wrote:
> On Tue, Jan 18, 2011 at 08:06:03AM -0500, Josef Bacik wrote:
> > Sounds good.  So which do we want, a new command or a new flag?  Thanks,
> 
> I'll wait for dave to chime in.  I think we should absolutely expose
> it as a fallocate flag, but if there's a good reason we can also expose
> it as a separate command.

My reasoning was that:

	a) it is consistent with other xfs_io allocation manipulation
	   command structures such as resvsp/unresvsp
	b) "punch" is less to type than "fallocate -p"
	c) self documenting in scripts e.g. -c "punch 4k 4k" is much
	   more obvious than -c "fallocate -p 4k 4k" and saves a man
	   page lookup when reading the script.
	d) punch as a top level command will show up in the "xfs_io
	   -c help", not require you to know it is a suboption of the
	   "falloc" command to find out how to use it.
	e) the xfs_io command does not have to have the same name
	   and structure as the underlying API that implements the
	   functionality the commands execute.


Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-01-18 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 12:52 [PATCH] xfsprogs: add fpunch command for hole punching via fallocate Josef Bacik
2011-01-18 12:51 ` Christoph Hellwig
2011-01-18 13:06   ` Josef Bacik
2011-01-18 13:12     ` Christoph Hellwig
2011-01-18 21:23       ` Dave Chinner [this message]
2011-01-19 11:38         ` Christoph Hellwig

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=20110118212303.GV28803@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=josef@redhat.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