From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 3/6] xfs: exact busy extent tracking
Date: Mon, 28 Mar 2011 08:10:54 -0400 [thread overview]
Message-ID: <20110328121054.GC18346@infradead.org> (raw)
In-Reply-To: <1301087060.2537.689.camel@doink>
On Fri, Mar 25, 2011 at 04:04:20PM -0500, Alex Elder wrote:
> > - * Insert a new extent into the busy tree.
>
> OK, to be honest I haven't re-read this entire block of
> comment text to identify what might be of value. But
> is there really *nothing* worth saving? Is the busy
> extent tree documented adequately elsewhere?
The old text doesn't really apply to the new code anymore. I'll see
if there's a place I can insert some more documentaion, but it already
has quite a lot of comments.
> > if (new->bno < busyp->bno) {
> > /* may overlap, but exact start block is lower */
>
> This comment isn't really right any more (BUG_ON that condition).
> > } else if (new->bno > busyp->bno) {
> > /* may overlap, but exact start block is higher */
>
> This one too.
Removed.
> > + continue;
> > + } else if (fbno >= bend) {
> > + rbp = rbp->rb_right;
> > + continue;
> > + }
> > +
>
> I was going to suggest:
> /* Extent overlaps busy extent */
>
> here, but I think that may not be the case any more if
> busyp->length is zero. Or rather, the extent may
> surround the zero-length busy extent (which I suppose
> could be considered overlap).
>
> If busyp->length is zero, I think the call to
> xfs_alloc_busy_try_reuse() is not needed; in fact,
> if it is already 0, that function will call
> rb_erase() on the entry again.
We will never see zero-length busy extents here. While they have
to remain on the per-transaction/cil_context list they are properly
removed from the rbtree.
> ...therefore this branch is always taken, and the code
> below this block to the end of the loop is not reached.
>
> Since this is the only place it's used, xfs_alloc_busy_try_reuse()
> might as well be defined as a void function.
>
> (Ahh, but now that I've looked at the later patches
> I see it gets used again later. I'm leaving my
> comments here nevertheless.)
Yes, it's changing in the next patch.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-28 12:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 19:55 [PATCH 0/6] [PATCH 0/6] more efficient busy extent handling and discard support Christoph Hellwig
2011-03-22 19:55 ` [PATCH 1/6] xfs: optimize AGFL refills Christoph Hellwig
2011-03-22 22:30 ` Alex Elder
2011-03-23 12:16 ` Christoph Hellwig
2011-03-25 21:03 ` Alex Elder
2011-03-28 12:07 ` Christoph Hellwig
2011-03-22 23:30 ` Dave Chinner
2011-03-23 12:16 ` Christoph Hellwig
2011-03-22 19:55 ` [PATCH 2/6] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-03-22 22:30 ` Alex Elder
2011-03-23 12:17 ` Christoph Hellwig
2011-03-25 21:03 ` Alex Elder
2011-03-28 12:07 ` Christoph Hellwig
2011-03-22 19:55 ` [PATCH 3/6] xfs: exact busy extent tracking Christoph Hellwig
2011-03-22 23:47 ` Dave Chinner
2011-03-23 12:24 ` Christoph Hellwig
2011-03-25 21:04 ` Alex Elder
2011-03-28 12:10 ` Christoph Hellwig [this message]
2011-03-22 19:55 ` [PATCH 4/6] xfs: allow reusing busy extents where safe Christoph Hellwig
2011-03-23 0:20 ` Dave Chinner
2011-03-23 12:26 ` Christoph Hellwig
2011-03-25 21:04 ` Alex Elder
2011-03-22 19:55 ` [PATCH 5/6] xfs: add online discard support Christoph Hellwig
2011-03-23 0:30 ` Dave Chinner
2011-03-23 12:31 ` Christoph Hellwig
2011-03-25 21:04 ` Alex Elder
2011-03-28 12:35 ` Christoph Hellwig
2011-03-22 19:55 ` [PATCH 6/6] xfs: make discard operations asynchronous Christoph Hellwig
2011-03-23 0:43 ` Dave Chinner
2011-03-28 12:44 ` Christoph Hellwig
2011-03-25 21:04 ` 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=20110328121054.GC18346@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--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.