From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: tracepoints in ext4 (and/or ext3?)
Date: Mon, 11 Aug 2008 23:23:35 -0400 [thread overview]
Message-ID: <20080812032335.GC21194@mit.edu> (raw)
In-Reply-To: <48A09E7F.7060605@redhat.com>
On Mon, Aug 11, 2008 at 03:18:07PM -0500, Eric Sandeen wrote:
> As just an initial inquiry, I'm wondering how people would feel about
> putting some tracepoints (trace_mark()) into ext[34] for monitoring the
> fs behavior.
I think it's a great idea! Do you have some specific tracepoints in
mind?
- Ted
next prev parent reply other threads:[~2008-08-12 3:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 20:18 tracepoints in ext4 (and/or ext3?) Eric Sandeen
2008-08-12 2:13 ` KOSAKI Motohiro
2008-08-12 3:23 ` Theodore Tso [this message]
2008-08-12 3:30 ` Eric Sandeen
2008-08-12 6:33 ` KOSAKI Motohiro
2008-08-12 13:19 ` Jose R. Santos
2008-08-12 13:57 ` Eric Sandeen
2008-08-12 16:32 ` Theodore Tso
2008-08-13 1:42 ` Eric Sandeen
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=20080812032335.GC21194@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@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