From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/4] xfs: exact busy extent tracking
Date: Thu, 21 Apr 2011 15:08:20 -0500 [thread overview]
Message-ID: <1303416500.2581.519.camel@doink> (raw)
In-Reply-To: <20110418070043.915023373@bombadil.infradead.org>
On Mon, 2011-04-18 at 02:59 -0400, Christoph Hellwig wrote:
> Update the extent tree in case we have to reuse a busy extent, so that it
> always is kept uptodate. This is done by replacing the busy list searches
> with a new xfs_alloc_busy_reuse helper, which updates the busy extent tree
> in case of a reuse. This allows us to allow reusing metadata extents
> unconditionally, and thus avoid log forces especially for allocation btree
> blocks.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
I think you finally got it Christoph.
I have one question--which I may have mentioned before--but
otherwise this looks good. I think the iterations have
resulted in a better result.
Reviewed-by: Alex Elder <aelder@sgi.com>
. . .
In xfs_alloc_busy_trim():
> @@ -2894,6 +2959,11 @@ fail:
> * re-check if the trimmed extent satisfies the minlen requirement.
> */
> spin_unlock(&args->pag->pagb_lock);
> + if (fbno != bno || flen != len) {
> + trace_xfs_alloc_busy_trim(args->mp, args->agno, bno, len,
> + fbno, flen);
> + }
> + trace_xfs_alloc_busy_trim(args->mp, args->agno, bno, len, fbno, 0);
> *rbno = fbno;
> *rlen = 0;
> }
I don't see why you do two trace calls here, the second
with 0 for the value of flen.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-21 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 6:59 [PATCH 0/4] improved busy extent handling V4 Christoph Hellwig
2011-04-18 6:59 ` [PATCH 1/4] xfs: optimize AGFL refills Christoph Hellwig
2011-04-18 6:59 ` [PATCH 2/4] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-04-18 6:59 ` [PATCH 3/4] xfs: exact busy extent tracking Christoph Hellwig
2011-04-21 20:08 ` Alex Elder [this message]
2011-04-22 4:13 ` Christoph Hellwig
2011-04-18 6:59 ` [PATCH 4/4] xfs: reduce the number of pagb_lock roundtrips in xfs_alloc_clear_busy Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2011-04-24 19:06 [PATCH 0/4] improved busy extent handling V5 Christoph Hellwig
2011-04-24 19:06 ` [PATCH 3/4] xfs: exact busy extent tracking Christoph Hellwig
2011-04-29 1:10 ` Dave Chinner
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=1303416500.2581.519.camel@doink \
--to=aelder@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.