From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 5/5] xfs: update busy extent tracing
Date: Tue, 29 Mar 2011 14:04:31 -0500 [thread overview]
Message-ID: <1301425471.3026.250.camel@doink> (raw)
In-Reply-To: <20110328210915.396135841@bombadil.infradead.org>
On Mon, 2011-03-28 at 17:06 -0400, Christoph Hellwig wrote:
> Add new tracepoint for the new busy extent handling helpers, and update the
> existing ones to use a common class. Also drop the busysearch tracepoint
> now that a plain busylist search only happens in a debug assert and the
> FITRIM handler.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Alex Elder <aelder@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-03-29 19:01 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 [this message]
2011-03-29 19:04 ` [PATCH 0/5] improved busy extent handling Alex Elder
2011-03-30 10:14 ` 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=1301425471.3026.250.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