From: Roland McGrath <roland@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sources.redhat.com, utrace-devel@redhat.com
Subject: Re: syscall tracing overheads: utrace vs. kprobes
Date: Tue, 28 Apr 2009 18:45:00 -0000 [thread overview]
Message-ID: <20090428181842.93694FC3C6@magilla.sf.frob.com> (raw)
In-Reply-To: Frank Ch. Eigler's message of Tuesday, 28 April 2009 14:16:39 -0400 <20090428181639.GD13893@redhat.com>
> Certainly, in general. But in this specific test, only the under-test
> system calls occurred in essnetially the whole system, so the overhead
> measurements were in a way the bare minimums imposed by the kprobes
> vs. utrace callback infrastructure itself.
Yes. That's why I meant to explain how these numbers are true but not
necessarily the numbers that matter.
> > In real situations [...] the distribution of overheads will be
> > quite different.
>
> Or rather, the basic overhead quanta measured above may be multiplied
> along several different axes.
Yes.
next prev parent reply other threads:[~2009-04-28 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 17:01 Frank Ch. Eigler
2009-04-28 18:10 ` Roland McGrath
2009-04-28 18:16 ` Frank Ch. Eigler
2009-04-28 18:45 ` Roland McGrath [this message]
2009-04-28 18:19 ` David Smith
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=20090428181842.93694FC3C6@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=utrace-devel@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).