From: Jeff Liu <jeff.liu@oracle.com>
To: Christoph Hellwig <hch@infradead.org>,
Dave Chinner <david@fromorbit.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [PATCH v2 02/10] xfs: consolidate xfs_bulkstat_single
Date: Tue, 22 Apr 2014 11:13:15 +0800 [thread overview]
Message-ID: <5355DE4B.2000009@oracle.com> (raw)
In-Reply-To: <20140421235249.GG18672@dastard>
On 04/22 2014 07:52 PM, Dave Chinner wrote:
> On Mon, Apr 21, 2014 at 07:11:48AM -0700, Christoph Hellwig wrote:
>> On Fri, Apr 18, 2014 at 08:58:21AM +0800, Jeff Liu wrote:
>>> From: Jie Liu <jeff.liu@oracle.com>
>>>
>>> In xfs_bulkstat_single(), call xfs_bulkstat_one() and xfs_bulkstat()
>>> would return different error if either failed, we'd better return the
>>> proper error in this case. Moreover, the function argument done is
>>> useless in terms of xfs_ioc_bulkstat(), hence we can get rid of it.
>>
>> I've looked at xfs_bulkstat_single I really can't see how falling back
>> to the full xfs_bulkstat could fix any error. We probably should just
>> get rid of the fallback and instead do something like the (lightly tested)
>> patch below:
>>
>> ---
>> From: Christoph Hellwig <hch@lst.de>
>> Subject: xfs: remove xfs_bulkstat_single
>>
>> xfs_bukstat_one doesn't have any failure case that would go away when
>> called through xfs_bulkstat, so remove the fallback and the now unessecary
>> xfs_bulkstat_single function.
>>
>> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> *nod*
>
> I like this approach :)
I reconsidered the call interface in xfs_fsr and xfs_io/parent.
Yep, your idea is better and the patch looks good to me.
Thanks,
-Jeff
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-04-22 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 0:58 [PATCH v2 02/10] xfs: consolidate xfs_bulkstat_single Jeff Liu
2014-04-21 14:11 ` Christoph Hellwig
2014-04-21 23:52 ` Dave Chinner
2014-04-22 3:13 ` Jeff Liu [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=5355DE4B.2000009@oracle.com \
--to=jeff.liu@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).