From: "Frank Ch. Eigler" <fche@redhat.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: systemtap@sourceware.org
Subject: Re: trace over network is supported?
Date: Fri, 10 Sep 2010 13:21:00 -0000 [thread overview]
Message-ID: <20100910132122.GB26765@redhat.com> (raw)
In-Reply-To: <4C89D4AB.7020902@hitachi.com>
Hi, Masami -
> > One can invoke stap over an ssh or similar connection, so to that
> > extent, "yes, it can.". What do you mean exactly?
>
> Yeah, I know about tracing over ssh connection, but
> that is too heavy to record high-freq system events
> (e.g. systemcalls).
>
> I meant that something like trace-data listener and
> sender over UDP or TCP.
If the heaviness comes from the encryption provided by ssh, then one
can tie stap straight to tcp/udp sockets with wrappers like netcat.
Beyond some copy-elimination a la splice(2), do you think there is
much to be done?
- FChE
prev parent reply other threads:[~2010-09-10 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 11:29 Masami Hiramatsu
2010-09-09 14:21 ` Frank Ch. Eigler
2010-09-10 6:48 ` Masami Hiramatsu
[not found] ` <AANLkTi=w3YfnZhKerWiSsd0RpcgJi61Xufr8JRXJzVO5@mail.gmail.com>
2010-09-10 7:46 ` Tim Beaulen
2010-09-10 13:21 ` Frank Ch. Eigler [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=20100910132122.GB26765@redhat.com \
--to=fche@redhat.com \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).