From: "Ted Ts'o" <tytso@mit.edu>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Perf can't deal with many tracepoints
Date: Wed, 27 Oct 2010 20:40:47 -0400 [thread overview]
Message-ID: <20101028004047.GH3194@thunk.org> (raw)
In-Reply-To: <4CC8C0D2.7060304@caviumnetworks.com>
On Wed, Oct 27, 2010 at 05:16:18PM -0700, David Daney wrote:
> Tracing is supposed to be low overhead. Forcing people to decode
> things like this at the trace point, may take more code and cause
> the trace data to be larger, making it slower than necessary.
>
> If there isn't a good reason to keep perf stupid, then making it
> smarter could be attractive.
Agreed. Although one argument against making perf smarter is that
certain things such as the dev_t MAJOR/MINOR split is an internal
abstraction that could potentially vary from kernel to kernel.
And the question is whether perf really should be so different that if
you boot a different kernel, you had better have the right perf
installed.
- Ted
next prev parent reply other threads:[~2010-10-28 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 23:20 Perf can't deal with many tracepoints Theodore Ts'o
2010-10-28 0:16 ` David Daney
2010-10-28 0:40 ` Ted Ts'o [this message]
2010-10-28 0:45 ` David Daney
2010-10-28 17:42 ` Frank Ch. Eigler
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=20101028004047.GH3194@thunk.org \
--to=tytso@mit.edu \
--cc=acme@redhat.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.