All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Rubin <mrubin@google.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Sharp <dhsharp@google.com>,
	linux-kernel@vger.kernel.org,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: Benchmarks of kernel tracing options (ftrace and ktrace)
Date: Thu, 18 Nov 2010 17:11:14 -0800	[thread overview]
Message-ID: <AANLkTimrgXbZxQKjapXkDgYRZqdZkfe1eUdFTAu=+Q8f@mail.gmail.com> (raw)
In-Reply-To: <1289950335.30543.8.camel@gandalf.stny.rr.com>

On Tue, Nov 16, 2010 at 3:32 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> Mike may have been confused ;-)

I am always confused.

> I did tell him that some ring buffer improvements did make it into the
> kernel. You might want to try the latest mainline again.

You told me that you had patches (in 2.6.37) I think that would allow
us to specifically improve the syscall tracing performance.

Can you point us at em?

mrubin

  reply	other threads:[~2010-11-19  1:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikfYy-kYb1=KbsYwHd0_vcf20d2nPSfFynugz8z@mail.gmail.com>
     [not found] ` <AANLkTikKwx6okpX4pxVzTvrVNm=KhUvLQGs0_ziwo6fX@mail.gmail.com>
2010-10-13 23:19   ` Benchmarks of kernel tracing options (ftrace and ktrace) David Sharp
2010-10-13 23:50     ` Steven Rostedt
2010-10-14  0:00       ` Mathieu Desnoyers
2010-10-14 11:27         ` Frederic Weisbecker
2010-10-14 18:04         ` Jason Baron
2010-11-16 23:27       ` David Sharp
2010-11-16 23:32         ` Steven Rostedt
2010-11-19  1:11           ` Michael Rubin [this message]
2010-11-19  1:41             ` Steven Rostedt

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='AANLkTimrgXbZxQKjapXkDgYRZqdZkfe1eUdFTAu=+Q8f@mail.gmail.com' \
    --to=mrubin@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhsharp@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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.