xfs
[Top] [All Lists]

Re: [PATCH 2/2] xfs_spaceman: Accounting for AGFL blocks

To: ADRS PICT <adrscube@xxxxxxxxx>
Subject: Re: [PATCH 2/2] xfs_spaceman: Accounting for AGFL blocks
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 29 Jan 2015 07:59:56 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CALJmpHP=vjz_ZY9sFpW8k2Y7TL+sz-WyjPeMoy4sM6XDTt8MTQ@xxxxxxxxxxxxxx>
References: <54c1c12e.230a460a.4729.11fc@xxxxxxxxxxxxx> <20150128015757.GT16552@dastard> <CALJmpHP=vjz_ZY9sFpW8k2Y7TL+sz-WyjPeMoy4sM6XDTt8MTQ@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>