This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Fwd: Any way to find the network usage by a process?
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Mike Mason <mmlnx at us dot ibm dot com>
- Cc: jrs at us dot ibm dot com, Irfan Habib <irfan dot habib at gmail dot com>, Linux kernel <linux-kernel at vger dot kernel dot org>, SystemTAP <systemtap at sources dot redhat dot com>
- Date: 05 Oct 2006 17:22:23 -0400
- Subject: Re: Fwd: Any way to find the network usage by a process?
- References: <3420082f0610030114o5b44b8ak7797483e02002614@mail.gmail.com> <3420082f0610030114o4c6998en907bccce81d28c59@mail.gmail.com> <452285FD.7010909@us.ibm.com> <45241F7A.5050501@us.ibm.com>
Mike Mason <mmlnx@us.ibm.com> writes:
> Here's a variation of Jose's script that uses the networking tapset
> and prints top-like output for transmits and receives. [...]
Thanks for posting it to the systemtap wiki.
Some minor style suggestions follow:
> [...]
> ifxmit_p[pid(), dev_name] ++
> ifxmit_b[pid(), dev_name] += length
These could be collapsed into a single statistics-aggregate array:
# ifxmit[pid(), dev_name] <<< length
Then the printing routine would use @count(ifxmit[...]) and @sum(ifxmit[...])
to extract the two values. Same of course for ifrecv.
> execname[pid()] = execname()
> user[pid()] = uid()
> ifdevs[pid(), dev_name] = dev_name
Calling pid() so many times is worse than calling it once and caching
the result in a local variable ("p = pid()").
The way that the script tracks pid-to-uid and pid-to-execname mappings
is not bad, though if that part were moved to new probes on fork or
exec, it would allow the network-related probes to run concurrently on
an SMP without fighting over locks.
- FChE