This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: some questions about systemtap
- From: "Peter Teoh" <htmldeveloper at gmail dot com>
- To: zshan <zshan at cse dot buaa dot edu dot cn>
- Cc: "wcohen at redhat dot com" <wcohen at redhat dot com>, "fche at redhat dot com" <fche at redhat dot com>, SystemTAP <systemtap at sources dot redhat dot com>, "Don Domingo" <ddomingo at redhat dot com>, haoqf <haoqf at buaa dot edu dot cn>, "沁汾郝" <haoqinfen at gmail dot com>
- Date: Tue, 25 Nov 2008 16:20:39 +0800
- Subject: Re: some questions about systemtap
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=hK54cwBGCSXg7xMw5tATz5f/i4YhXi6/8U35NV3Ldyw=; b=L6BtpvTabyqKFMLMJ6bPs49P26l0FbaGJS3d0z4dX3Tzd7URtBjNRbC5UreE9IrXQ5 gq9qe9iofp6OQBLNjjy7CNl2QYCVvv/iOuuUacbSGihdPOn0bMZL52zENNTbjJui8LJm BMY3J5GOoUO6MMfjuaJmyzS6YYcwDadLBpl34=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=vozNe2L5MiFZwj9hoTXsZR64cfjGnsIYyDmiFm1Vvzwc4g89jQLhCGIIPOnmhI3XhW RAs0pLBYoILXtrsmJDJZ1tDlYsTBswihveYCTEO0yHe1dX4lTq/UsDXw2eFsROwWaBqg j9ZSDiwuiVs+VKuh9dEot9uVCFJRk1TGNvC54=
- References: <200811250222241096246@cse.buaa.edu.cn>
kernel path tracing is what systemtap is good at, for for TCP -
evolution of stack trace indicate something of the kernel path
traversed:
0xc0612dc7 : tcp_poll+0x1/0x133 [kernel]
0xc04a2578 : do_sys_poll+0x210/0x3c3 [kernel]
0xc04a287a : sys_poll+0x45/0x8f [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_poll
0xc0620c8e : tcp_v4_init_sock+0x1/0x14b [kernel]
0xc05e3a93 : __sock_create+0x11d/0x19d [kernel]
0xc05e3b5a : sock_create+0x29/0x2e [kernel]
0xc05e3d63 : sys_socket+0x31/0x5f [kernel]
0xc05e46c8 : sys_socketcall+0x73/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_v4_init_sock
0xc0620185 : tcp_init_xmit_timers+0x1/0x1f [kernel]
0xc062da65 : inet_create+0x24c/0x26f [kernel]
0xc05e3a93 : __sock_create+0x11d/0x19d [kernel]
0xc05e3b5a : sock_create+0x29/0x2e [kernel]
0xc05e3d63 : sys_socket+0x31/0x5f [kernel]
0xc05e46c8 : sys_socketcall+0x73/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_init_xmit_timers
0xc0620cc6 : tcp_v4_init_sock+0x39/0x14b [kernel]
0xc062da65 : inet_create+0x24c/0x26f [kernel]
0xc05e3a93 : __sock_create+0x11d/0x19d [kernel]
0xc05e3b5a : sock_create+0x29/0x2e [kernel]
0xc05e3d63 : sys_socket+0x31/0x5f [kernel]
0xc05e46c8 : sys_socketcall+0x73/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_prequeue_init
0xc06237a3 : tcp_v4_connect+0x1/0x4c2 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_v4_connect
0xc0613a50 : tcp_set_state+0x1/0xe1 [kernel]
0xc062d489 : inet_stream_connect+0x8f/0x1f9 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_set_state
0xc061de43 : tcp_connect+0x1/0x3a0 [kernel]
0xc062d489 : inet_stream_connect+0x8f/0x1f9 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_connect
0xc061de51 : tcp_connect+0xf/0x3a0 [kernel]
0xc0623c0c : tcp_v4_connect+0x46a/0x4c2 [kernel]
0xc062d489 : inet_stream_connect+0x8f/0x1f9 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_connect_init
0xc0620c1d : tcp_v4_md5_lookup+0x1/0x3a [kernel]
0xc0623c0c : tcp_v4_connect+0x46a/0x4c2 [kernel]
0xc062d489 : inet_stream_connect+0x8f/0x1f9 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_v4_md5_lookup
0xc0620c27 : tcp_v4_md5_lookup+0xb/0x3a [kernel]
0xc061de77 : tcp_connect+0x35/0x3a0 [kernel]
0xc0623c0c : tcp_v4_connect+0x46a/0x4c2 [kernel]
0xc062d489 : inet_stream_connect+0x8f/0x1f9 [kernel]
0xc05e4034 : sys_connect+0x65/0x82 [kernel]
0xc05e46e8 : sys_socketcall+0x93/0x192 [kernel]
0xc0403b6b : ia32_sysenter_target+0x7b/0x138 [kernel]
--->tcp_v4_md5_do_lookup
but for time measurement...u need another tool, possibly some network
benchmarking tool.
2008/11/25 zshan <zshan@cse.buaa.edu.cn>:
> Hello,
>
> I and my mentor Mr hao (cc-ed in the mail )want to research on is the
> network I/O, which including dececting the network I/O path and the time
> each process takes durning one network I/O request .
>
> We wonder whether it is feasible ?
>
> Any ideas ?
>
> thank you ~
>
> 2008-11-25
> ________________________________
> Regrads
> zengshan
>
>
>
--
Regards,
Peter Teoh
Ernest Hemingway - "Never mistake motion for action."