public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Theodore Ts'o" <tytso@mit.edu>,
	"Steven Rostedt" <rostedt@goodmis.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Linux Kernel Developers List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] ext4: Convert instrumentation from markers to tracepoints
Date: Mon, 13 Apr 2009 23:37:45 +0200	[thread overview]
Message-ID: <20090413213745.GC8514@elte.hu> (raw)
In-Reply-To: <1239557566-3411-2-git-send-email-tytso@mit.edu>


* Theodore Ts'o <tytso@mit.edu> wrote:

> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
>  fs/ext4/ext4.h                    |   22 +--
>  fs/ext4/ext4_i.h                  |   12 -
>  fs/ext4/fsync.c                   |    8 +-
>  fs/ext4/ialloc.c                  |   17 +-
>  fs/ext4/inode.c                   |   79 ++---
>  fs/ext4/mballoc.c                 |   84 ++---
>  fs/ext4/mballoc.h                 |   68 +----
>  fs/ext4/super.c                   |    6 +-
>  include/linux/ext4_trace_types.h  |  108 ++++++
>  include/trace/ext4.h              |    8 +
>  include/trace/ext4_event_types.h  |  690 +++++++++++++++++++++++++++++++++++++
>  include/trace/trace_event_types.h |    1 +
>  include/trace/trace_events.h      |    1 +
>  13 files changed, 886 insertions(+), 218 deletions(-)
>  create mode 100644 include/linux/ext4_trace_types.h
>  create mode 100644 include/trace/ext4.h
>  create mode 100644 include/trace/ext4_event_types.h

Really nice stuff!

A general, high-level observation: it is visible that the conversion 
to TRACE_EVENTS() does increase the total linecount, but it also 
removes code from the most often used source code areas 
(fs/ext4/*.c) - and using an intuitive function-call-alike 
single-line tracepoint there.

I'd call that a positive effect.

It would still be nice to compact the 690 lines of (out of line) 
ext4_event_types.h definitions some more - and i think we'll be able 
to do it without affecting the usage sites.

OTOH, even those bits look fairly readable, and there's a fair 
amount of bang-for-bucks ratio - these tracepoints give us:

      - integrated tracepoints
      - zero-copy and per-cpu splice() based tracing
      - binary tracing without printf overhead
      - structured logging records exposed under /debug/tracing/events
      - trace events embedded in function tracer output and other plugins
      - user-defined, per tracepoint filter expressions

... so even if we were to keep the 690 lines of overhead with no 
further compacting, it still looks like a good deal to me, all 
things considered.

	Ingo

  reply	other threads:[~2009-04-13 21:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 19:51 [PATCH, RFC 0/3] Improvements to the tracing documentation Theodore Ts'o
2009-04-11 19:51 ` [PATCH, RFC 1/3] tracing: Update documentation references in kernel/trace/Kconfig Theodore Ts'o
2009-04-11 19:51   ` [PATCH, RFC 2/3] tracing: Document the event tracing system Theodore Ts'o
2009-04-11 19:51     ` [PATCH, RFC 3/3] tracing: Add documentation for the power tracer Theodore Ts'o
2009-04-11 20:44       ` Joe Perches
2009-04-11 21:48       ` Arjan van de Ven
2009-04-12  9:28       ` [tip:tracing/core] " Theodore Ts'o
2009-04-12 13:00       ` Theodore Ts'o
2009-04-12  9:27     ` [tip:tracing/core] tracing: Document the event tracing system Theodore Ts'o
2009-04-12  9:40       ` Cyrill Gorcunov
2009-04-12 13:00     ` Theodore Ts'o
2009-04-12  9:25 ` [PATCH, RFC 0/3] Improvements to the tracing documentation Ingo Molnar
2009-04-12 12:15   ` Theodore Tso
2009-04-12 13:01     ` Ingo Molnar
2009-04-12 17:23       ` Theodore Tso
2009-04-12 17:32         ` [PATCH 1/2] jbd2: Convert instrumentation from markers to tracepoints Theodore Ts'o
2009-04-12 17:32           ` [PATCH 2/2] ext4: " Theodore Ts'o
2009-04-13 21:37             ` Ingo Molnar [this message]
2009-04-13 21:31         ` [PATCH, RFC 0/3] Improvements to the tracing documentation Ingo Molnar
2009-04-13 22:35           ` Theodore Tso
2009-04-13 22:55             ` Ingo Molnar
2009-04-13 23:39               ` Theodore Tso
2009-04-13 23:47                 ` Ingo Molnar
2009-04-14  5:22               ` Tom Zanussi

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=20090413213745.GC8514@elte.hu \
    --to=mingo@elte.hu \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tytso@mit.edu \
    /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