[PATCH 2/6] xfs: do not immediately reuse busy extent ranges

Christoph Hellwig hch at infradead.org
Mon Mar 28 07:07:57 CDT 2011


On Fri, Mar 25, 2011 at 04:03:19PM -0500, Alex Elder wrote:
> > +			 * Can be trimmed to:
> > +			 *    +-------+        OR         +-------+
> > +			 *    fbno fend                   fbno fend
> > +			 *
> > +			 * We prefer the lower bno extent because the next
> > +			 * allocation for this inode will use "end" as the
> > +			 * target for first block.  If the busy segment has
> 
> ...will use the updated value of fend as the target...

I've replaced all these comments based on the text you replied to the
last round (finally..)




More information about the xfs mailing list