From: Dave Chinner <david@fromorbit.com>
To: ADRS PICT <adrscube@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfs_spaceman: Accounting for AGFL blocks
Date: Thu, 29 Jan 2015 07:59:56 +1100 [thread overview]
Message-ID: <20150128205956.GA6282@dastard> (raw)
In-Reply-To: <CALJmpHP=vjz_ZY9sFpW8k2Y7TL+sz-WyjPeMoy4sM6XDTt8MTQ@mail.gmail.com>
On Wed, Jan 28, 2015 at 06:35:22PM +0530, ADRS PICT wrote:
> On Wed, Jan 28, 2015 at 7:27 AM, Dave Chinner <david@fromorbit.com> wrote:
> > Hmmm - I think something is still missing - what are the sagbno and
> > eagbno parameters supposed to do?
>
> Actually the parameters sagbno and eagbno are not needed in this
> function and can be excluded.
Why? Don't we still have to check the blocks found on the AGFL fll
within the range requested by the user, like we do for every extent
found in the btree?
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-01-28 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 3:34 [PATCH 2/2] xfs_spaceman: Accounting for AGFL blocks Dhruvesh Rathore
2015-01-28 1:57 ` Dave Chinner
2015-01-28 13:05 ` ADRS PICT
2015-01-28 20:59 ` Dave Chinner [this message]
[not found] ` <CALJmpHOFVZer7YL8Kek6jk2U8f7JyBrJknYzVhyowht_EGm7DQ@mail.gmail.com>
2015-01-29 3:48 ` Fwd: " Dhruvesh Rathore
2015-01-29 12:58 ` Dhruvesh Rathore
[not found] ` <20150130013456.GA4251@dastard>
2015-01-30 8:25 ` Dhruvesh Rathore
2015-02-02 6:34 ` Dhruvesh Rathore
-- strict thread matches above, loose matches on Subject: below --
2015-01-16 12:10 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=20150128205956.GA6282@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