public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: tracepoints in ext4 (and/or ext3?)
Date: Tue, 12 Aug 2008 12:32:32 -0400	[thread overview]
Message-ID: <20080812163232.GC8857@mit.edu> (raw)
In-Reply-To: <20080812081954.5f5eeb10@gara>

On Tue, Aug 12, 2008 at 08:19:54AM -0500, Jose R. Santos wrote:
> 
> Good idea, although Im not sure if ext[34] is the best place we should
> start putting markers though.

I can think of ext3/4 specific markers that would be useful for people
who are tuning our filesystems for performance.  This would include
when we start and end tranactions, when we force a checkpoint, when we
create and, extend, and finish using a handle in the jbd layer.

In the ext4 itself, knowing when we are mapping delayed allocations
would be useful, as well as when we freeze and unfreeze a filesystem
(i.e., for snapshots).

There are a lot of other tracepoints that probably do make more sense
to be put in the VFS layer, although on thing that would be *really*
nice is some semantic sugar in Systemtap or in a Systemtap tapset so
that we only trigger the tracepoints for a particular filesystem.

     	     	     	 	     	   - Ted

  parent reply	other threads:[~2008-08-12 16:32 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
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 [this message]
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=20080812163232.GC8857@mit.edu \
    --to=tytso@mit.edu \
    --cc=jrs@us.ibm.com \
    --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