From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/5] improved busy extent handling
Date: Tue, 29 Mar 2011 14:04:35 -0500 [thread overview]
Message-ID: <1301425475.3026.251.camel@doink> (raw)
In-Reply-To: <20110328210614.832613417@bombadil.infradead.org>
On Mon, 2011-03-28 at 17:06 -0400, Christoph Hellwig wrote:
> This series optimizes how XFS deals with busy extents. It starts to
> track them exactly, and allows reuses where possible (metadata to metadata)
> or else tries to avoid busy extents during allocations. This means
> we don't have a single log force due to busy extents during either
> xfstests, compilebench or postmark on my testsystem, which can easily
> be tracked using the new tracepoints added in the last patch.
>
> This is a repost of the previous series and should address all review
> comments. The discard support, which relies on the exact busy extent
> tracking has been dropped temporarily until I can fix up some issues
> that I found during testing.
I've reviewed the series and it looks good to me.
Unless someone else has comments that deserve some
action I can take these in as-is. I'll wait for
a bit though, to let the 2.6.39 merge window settle.
I'm still curious what this (clipping busy blocks
from consideration when allocating) will do to
allocation patterns. Probably not much except in
somewhat extreme conditions (when they already
won't likely be that good). The "goodness" of
allocation patterns are a bit hard to characterize
anyway.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-29 19:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 21:06 [PATCH 0/5] improved busy extent handling Christoph Hellwig
2011-03-28 21:06 ` [PATCH 1/5] xfs: optimize AGFL refills Christoph Hellwig
2011-03-29 19:04 ` Alex Elder
2011-03-28 21:06 ` [PATCH 2/5] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-03-29 19:04 ` Alex Elder
2011-03-28 21:06 ` [PATCH 3/5] xfs: exact busy extent tracking Christoph Hellwig
2011-03-29 19:04 ` Alex Elder
2011-03-28 21:06 ` [PATCH 4/5] xfs: allow reusing busy extents where safe Christoph Hellwig
2011-03-29 19:04 ` Alex Elder
2011-03-31 8:30 ` Christoph Hellwig
2011-03-28 21:06 ` [PATCH 5/5] xfs: update busy extent tracing Christoph Hellwig
2011-03-29 19:04 ` Alex Elder
2011-03-29 19:04 ` Alex Elder [this message]
2011-03-30 10:14 ` [PATCH 0/5] improved busy extent handling Christoph Hellwig
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=1301425475.3026.251.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