| To: | Alex Elder <aelder@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 1/6] xfs: optimize AGFL refills |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 28 Mar 2011 08:07:22 -0400 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <1301086981.2537.687.camel@doink> |
| References: | <20110322195550.260682574@xxxxxxxxxxxxxxxxxxxxxx> <20110322200137.280301318@xxxxxxxxxxxxxxxxxxxxxx> <1300833051.2875.275.camel@doink> <20110323121613.GA468@xxxxxxxxxxxxx> <1301086981.2537.687.camel@doink> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
> The reason it was not obvious is because the case you're > treating is specifically when moving extents (blocks, > really) between the free list and the free btrees, in > xfs_alloc_fix_freelist(). You still need to force it > out when allocating and freeing "actually used" blocks, > which could also be considered "moving blocks from/to > the AGFL." I've updated the comment to make that more clear. |
| Previous by Date: | Re: 2.6.38.1: CPU#0 stuck for 67s! / xfs_ail_splice, Justin Piszcz |
|---|---|
| Next by Date: | Re: [PATCH 2/6] xfs: do not immediately reuse busy extent ranges, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 1/6] xfs: optimize AGFL refills, Alex Elder |
| Next by Thread: | Re: [PATCH 1/6] xfs: optimize AGFL refills, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |