From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Tracing support
Date: Wed, 15 Apr 2009 10:13:06 +0100 [thread overview]
Message-ID: <1239786786.3377.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1239726339.29604.52.camel@localhost.localdomain>
Hi,
On Tue, 2009-04-14 at 17:25 +0100, Steven Whitehouse wrote:
> >From c154c0500fa6f5fad6eb95cf9f1b578a5cd24525 Mon Sep 17 00:00:00 2001
> From: Steven Whitehouse <swhiteho@redhat.com>
> Date: Tue, 14 Apr 2009 16:13:55 +0100
> Subject: [PATCH] GFS2: Tracing support
>
> This is my initial attempt at tracing support for GFS2. There are three
> major themes covering glocks, logging and bmap/alloc. It seems to work
> ok on its own, although the plan is to be able to use it in conjunction
> with blktrace in order to provide a means of testing correctness and
> performance analysis of GFS2.
>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
>
Some further notes:
Firstly there seems to be an issue with formatting when blktrace and one
or more of the events tracers are used in combination. There are patches
being proposed at the moment to solve this issue, so it shouldn't be too
long before that is fixed.
Also there are patches in the works to merge the two tracing headers
into one. That means that this patch will have to change too. It might
be easier for me to submit this via the tracing tree, rather than the
gfs2 tree bearing in mind the number of changes going on in the tracing
tree right now.
Steve.
prev parent reply other threads:[~2009-04-15 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 16:25 [Cluster-devel] GFS2: Tracing support Steven Whitehouse
2009-04-15 9:13 ` Steven Whitehouse [this message]
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=1239786786.3377.6.camel@localhost.localdomain \
--to=swhiteho@redhat.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