From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Nikolay Borisov <nborisov@suse.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
eguan@redhat.com, darrick.wong@oracle.com
Subject: Re: [PATCH v3 2/2] fiemap: Implement ranged query
Date: Wed, 15 Nov 2017 07:52:26 +1100 [thread overview]
Message-ID: <20171114205226.GB4094@dastard> (raw)
In-Reply-To: <bbfdb7c8-81a7-0a42-ccfc-003f3b89de9b@sandeen.net>
On Tue, Nov 14, 2017 at 07:31:34AM -0600, Eric Sandeen wrote:
>
>
> On 11/14/17 12:32 AM, Nikolay Borisov wrote:
> >
> >
> > On 14.11.2017 00:22, Eric Sandeen wrote:
> >> On 11/13/17 4:05 PM, Nikolay Borisov wrote:
>
> ...
>
> >>> You are right this is a bit ugly, but it seems more consistend to me,
> >>> rather than something like
> >>>
> >>> xfs_io -c "fiemap -r -n 10 -v 4k 10k" for example. And the reason why
> >>> I'm using this hackish way and not declaring r as r: in getopt is
> >>> because getopt doesn't recognise when a parameter takes more than 1
> >>> argument.
> >>
> >> Sorry for chiming in so late after all the go-rounds, but:
> >>
> >> Why not just drop -r entirely, and make fiemap go into ranged mode iff a
> >> range is specified at the end of the command, i.e.:
> >>
> >> fiemap [ -alv ] [ -n nx ] [ offset length ]
> >
> > V2 was like that but it required some changing to the generic code which
> > detects the presence of this feature and Dave objected hence v3.
>
> Ok, sorry for being so behind and rehashing old discussions. Let me look
> at that.
I suggested "-r" because of the fact that you can't detect optional
parameters in fstests without jumping through really nasty hoops
involving regex line noise.
Cheers,
Daves.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-11-14 20:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 15:47 [PATCH v3 1/2] fiemap: Factor out actual fiemap call code Nikolay Borisov
2017-11-13 15:47 ` [PATCH v3 2/2] fiemap: Implement ranged query Nikolay Borisov
2017-11-13 21:44 ` Dave Chinner
2017-11-13 22:05 ` Nikolay Borisov
2017-11-13 22:22 ` Eric Sandeen
2017-11-14 6:32 ` Nikolay Borisov
2017-11-14 13:31 ` Eric Sandeen
2017-11-14 20:52 ` Dave Chinner [this message]
2017-11-14 20:54 ` Eric Sandeen
2017-11-13 15:50 ` [PATCH v3 1/2] generic: Adjust generic test outputs for new fiemap imeplementation Nikolay Borisov
2017-11-13 15:50 ` [PATCH v3 2/2] xfs: initial fiemap range query test Nikolay Borisov
2017-11-14 14:36 ` Eric Sandeen
2017-11-15 7:02 ` Nikolay Borisov
2017-11-14 20:10 ` Darrick J. Wong
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=20171114205226.GB4094@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=sandeen@sandeen.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 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).