All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: unconditionally enable the trace buffer
Date: Tue, 25 Oct 2005 10:40:18 -0600	[thread overview]
Message-ID: <435E5FF2.5070502@hp.com> (raw)

Last month Mark Williamson sent out a patch to unconditionally enable 
the trace buffer. I'd like to suggest that his patch be accepted and 
merged. I have performed some simple benchmarks to quantify the overhead 
associated with the trace buffer and calls, and found a negligable 
performance loss due to them. The actual number was .069%, and was 
gotten by timing a simple cpu-intensive task running with trace buffers 
compiled in and again with trace buffers not compiled in. It's important 
for us to have the trace buffer functionality totally enabled by 
default, so we can depend on its availability for running XenMon without 
requiring recompiling and rebooting.

Thanks,
Rob Gardner (HP)

             reply	other threads:[~2005-10-25 16:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 16:40 Rob Gardner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-27 19:45 unconditionally enable the trace buffer Ian Pratt
2005-10-27 22:08 ` Rob Gardner
2005-10-27 23:21   ` Mark Williamson
2005-10-28  0:24 Ian Pratt
2005-10-28  6:45 ` Rob Gardner

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=435E5FF2.5070502@hp.com \
    --to=rob.gardner@hp.com \
    --cc=xen-devel@lists.xensource.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 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.