From: "Michael Fischer" <fischi@epygi.de>
To: <acurtis@onz.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: Debugging Network Performance
Date: Tue, 4 Jun 2002 17:05:41 +0200 [thread overview]
Message-ID: <OEEHJMIIDJHHMFGGDNGDEEEOCOAA.fischi@epygi.de> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFOEBLDIAA.acurtis@onz.com>
Hello,
> Any idea who the network stack maintainer is? Perhaps they have something
> that timestamps a packets progress through the pipeline.
i dont know about what/if they are using but when i had to do something
similar i patched my kernlel with the LTT package
(http://www.opersys.com/LTT/). They have some built in tracepoints which are
usefull + added some user defined trace events at different points within
the driver and the stack. With a sequence number in the package which is
copied to the trace you can pretty much follow and timestamp the way of the
packet through the system.
Of cause this is affecting the performance a bit but it may give you some
idea where the packet spents most of the time.
Best regards, Michael
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-04 15:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 14:35 Debugging Network Performance Mark Wisner
2002-06-04 14:46 ` Allen Curtis
2002-06-04 15:05 ` Michael Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 12:18 Jean-Denis Boyer
2002-06-05 13:35 ` Allen Curtis
2002-06-05 5:18 Bill Fink
2002-06-05 13:16 ` Allen Curtis
2002-06-05 13:56 ` Bill Fink
2002-06-04 11:12 Mark Wisner
2002-06-04 13:30 ` Allen Curtis
2002-06-04 4:34 Allen Curtis
2002-06-04 9:50 ` Kenneth Johansson
2002-06-04 3:27 Allen Curtis
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=OEEHJMIIDJHHMFGGDNGDEEEOCOAA.fischi@epygi.de \
--to=fischi@epygi.de \
--cc=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).