public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@hitachi.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel@vger.kernel.org,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: ivring driver
Date: Tue, 12 Jun 2012 11:36:57 +0900	[thread overview]
Message-ID: <4FD6AB49.3010809@hitachi.com> (raw)
In-Reply-To: <20120605152947.GA21787@Krystal>

(2012/06/06 0:29), Mathieu Desnoyers wrote:
> Hi Yoshihiro,
>
> I stumbled on your post on ivring (https://lkml.org/lkml/2012/6/5/143)
> for buffering trace data from guest to host. I notice that it would be
> very interesting to see a comparison of its performance against:
>
> - ftrace ring buffer
> - perf ring buffer
> - lttng 2.0 ring buffer
> - lttng-ust 2.0 (user-space tracing) ring buffer

Hi Mathieu. Thank you for commenting on how to compare among
ring-buffer's performances. And sorry, I'm late for replying to you.

> Comparing only with network-related mechanisms does not seem to provide
> a complete picture of where it stands wrt other ring buffers out there.
>
> One of the metric we have used in the past is the number of nanoseconds
> it takes to write a single event, based on a test that writes lots of
> events into various buffer sizes, into flight recorder mode buffers
> (which overwrites oldest information on buffer full condition, with data
> collection to disk disabled, to remove I/O from the picture -- I/O can
> then be performed in "snapshot" mode, after some error condition is
> detected).

OK, I see. When the overhead of ring-buffers will be evaluated in
the next, I may use the metric as a reference.

Thank you,

-- 
Yoshihiro YUNOMAE
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: yoshihiro.yunomae.ez@hitachi.com

      reply	other threads:[~2012-06-12  2:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 15:29 ivring driver Mathieu Desnoyers
2012-06-12  2:36 ` Yoshihiro YUNOMAE [this message]

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=4FD6AB49.3010809@hitachi.com \
    --to=yoshihiro.yunomae.ez@hitachi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox