From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/6] xfs: do not immediately reuse busy extent ranges
Date: Thu, 27 Jan 2011 17:20:06 -0600 [thread overview]
Message-ID: <1296170406.7651.523.camel@doink> (raw)
In-Reply-To: <20110121092550.933551564@bombadil.infradead.org>
On Fri, 2011-01-21 at 04:22 -0500, Christoph Hellwig wrote:
> Every time we reallocate a busy extent, we cause a synchronous log force
> to occur to ensure the freeing transaction is on disk before we continue
> and use the newly allocated extent. This is extremely sub-optimal as we
> have to mark every transaction with blocks that get reused as synchronous.
>
> Instead of searching the busy extent list after deciding on the extent to
> allocate, check each candidate extent during the allocation decisions as
> to whether they are in the busy list. If they are in the busy list, we
> trim the busy range out of the extent we have found and determine if that
> trimmed range is still OK for allocation. In many cases, this check can
> be incorporated into the allocation extent alignment code which already
> does trimming of the found extent before determining if it is a valid
> candidate for allocation.
>
> [hch: merged two earlier patches from Dave and fixed various bugs]
>
> Signed-off-by: Dave Chinner <david@fromorbit.com>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
You know, I must really not be looking at this right, because
the way I am interpreting your xfs_alloc_busy_search_trim(),
it's just plain wrong. Perhaps it arrives at an OK result
anyway, but please take a look to see if I'm just confused.
I have a few other comments, not as important.
Generally the rest of it looks good.
I'll pick up with the rest of the series tomorrow.
-Alex
> Index: xfs/fs/xfs/xfs_alloc.c
> ===================================================================
> --- xfs.orig/fs/xfs/xfs_alloc.c 2011-01-17 22:05:27.146004341 +0100
> +++ xfs/fs/xfs/xfs_alloc.c 2011-01-18 13:04:30.239023407 +0100
. . .
> @@ -2654,6 +2730,71 @@ xfs_alloc_busy_search(
> return match;
> }
>
> +/*
> + * For a given extent [fbno, flen], search the busy extent list
> + * to find a subset of the extent that is not busy.
> + */
> +void
> +xfs_alloc_busy_search_trim(
> + struct xfs_mount *mp,
> + struct xfs_perag *pag,
> + xfs_agblock_t fbno,
> + xfs_extlen_t flen,
> + xfs_agblock_t *rbno,
> + xfs_extlen_t *rlen)
> +{
> + struct rb_node *rbp;
> + xfs_agblock_t bno = fbno;
> + xfs_extlen_t len = flen;
> +
I don't know if it's important, but you could ASSERT(flen > 0) here.
> + spin_lock(&pag->pagb_lock);
> + rbp = pag->pagb_tree.rb_node;
> + while (rbp) {
while (rbp && len) {
> + struct xfs_busy_extent *busyp =
> + rb_entry(rbp, struct xfs_busy_extent, rb_node);
> + xfs_agblock_t end = bno + len;
> + xfs_agblock_t bend = busyp->bno + busyp->length;
> +
> + if (bno + len <= busyp->bno) {
> + rbp = rbp->rb_left;
> + continue;
> + } else if (bno >= busyp->bno + busyp->length) {
> + rbp = rbp->rb_right;
> + continue;
> + }
> +
> + if (busyp->bno < bno) {
> + /* start overlap */
> + ASSERT(bend >= bno);
ASSERT(bend > bno);
> + ASSERT(bend <= end);
> + len -= bno - bend;
NO: len -= bend - bno;
> + bno = bend;
> + } else if (bend > end) {
> + /* end overlap */
> + ASSERT(busyp->bno >= bno);
> + ASSERT(busyp->bno < end);
> + len -= bend - end;
NO: len -= end - busyp->bn;
> + } else {
> + /* middle overlap - return larger segment */
> + ASSERT(busyp->bno >= bno);
> + ASSERT(bend <= end);
> + len = busyp->bno - bno;
> + if (len >= end - bend) {
> + /* use first segment */
> + len = len;
> + } else {
> + /* use last segment */
> + bno = bend;
> + len = end - bend;
> + }
/* Use the first segment... */
len = busp->bno - bno;
if (len < end - bend) {
/* unless the second is larger */
bno = bend;
len = end - bend;
}
> + }
> + }
> + spin_unlock(&pag->pagb_lock);
> +
> + *rbno = bno;
> + *rlen = len;
> +}
> +
> void
> xfs_alloc_busy_clear(
> struct xfs_mount *mp,
. . .
> Index: xfs/fs/xfs/linux-2.6/xfs_discard.c
> ===================================================================
> --- xfs.orig/fs/xfs/linux-2.6/xfs_discard.c 2011-01-17 22:06:13.004005040 +0100
> +++ xfs/fs/xfs/linux-2.6/xfs_discard.c 2011-01-17 22:14:09.133005668 +0100
> @@ -77,8 +77,8 @@ xfs_trim_extents(
> * enough to be worth discarding.
> */
> while (i) {
> - xfs_agblock_t fbno;
> - xfs_extlen_t flen;
> + xfs_agblock_t fbno, tbno;
> + xfs_extlen_t flen, tlen;
Does "f" represent "found" and "t" represent "trimmed" here?
(Just curious--it's fine.)
>
> error = xfs_alloc_get_rec(cur, &fbno, &flen, &i);
> if (error)
> @@ -90,7 +90,7 @@ xfs_trim_extents(
> * Too small? Give up.
> */
> if (flen < minlen) {
> - trace_xfs_discard_toosmall(mp, agno, fbno, flen);
> + trace_xfs_discard_toosmall(mp, agno, tbno, flen);
"tbno" appears to be possibly used before set here. At this point
don't you actually want the found block number anyway?
> goto out_del_cursor;
> }
>
. . .
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-01-27 23:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 9:22 [PATCH 0/6] do not reuse busy extents Christoph Hellwig
2011-01-21 9:22 ` [PATCH 1/6] xfs: clean up the xfs_alloc_compute_aligned calling convention Christoph Hellwig
2011-01-25 4:23 ` Dave Chinner
2011-01-27 23:21 ` Alex Elder
2011-01-21 9:22 ` [PATCH 3/6] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-01-27 23:20 ` Alex Elder [this message]
2011-01-28 1:58 ` Dave Chinner
2011-01-28 16:19 ` Alex Elder
2011-01-29 0:25 ` Dave Chinner
2011-01-21 9:22 ` [PATCH 4/6] xfs: optimize xfs_alloc_fix_freelist Christoph Hellwig
2011-01-28 5:36 ` Dave Chinner
2011-01-28 5:51 ` Dave Chinner
2011-01-28 22:17 ` Alex Elder
2011-01-21 9:22 ` [PATCH 5/6] xfs: do not classify freed allocation btree blocks as busy Christoph Hellwig
2011-01-28 6:33 ` Dave Chinner
2011-01-28 22:17 ` Alex Elder
2011-02-01 23:02 ` Alex Elder
2011-01-21 9:22 ` [PATCH 6/6] xfs: remove handling of duplicates the busy extent tree Christoph Hellwig
2011-02-01 23:02 ` Alex Elder
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=1296170406.7651.523.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox