From: "Allen Curtis" <acurtis@onz.com>
To: "Mark Wisner" <markwiz@us.ibm.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: Debugging Network Performance
Date: Tue, 4 Jun 2002 06:30:16 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFIEBKDIAA.acurtis@onz.com> (raw)
In-Reply-To: <OFA5A51CBB.95D864D5-ON85256BCE.003C5665@raleigh.ibm.com>
> Netperf can give you a vary detailed report about network performance. If
> you think your problem is related to network hardware problems,
> look at the
> errors listed in "ifconfig". This should tell you if you are getting bad
> packets or dropping packets.
I did fix a problem in the driver and now there are no error reported by
ifconfig.
> If you think it is a kernel problem some benchmarks may help you narrow
> down the problem. Networks are pretty fluid and sometimes hard to get
> reproducible results. When I try to determine driver/kernel network
> perfomance I try to use an isolated network where I have control over all
> traffic or I use test hardware such as IXIA or Smartbits.
All testing is done on an isolated network. I do not believe that the
problem is in the driver itself. The driver has not changed significantly. I
do need to check the error path since it appears that errors actually help
performance.
What is the best way to track packet processing through the kernel?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-04 13:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 11:12 Debugging Network Performance Mark Wisner
2002-06-04 13:30 ` Allen Curtis [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 14:35 Mark Wisner
2002-06-04 14:46 ` Allen Curtis
2002-06-04 15:05 ` Michael Fischer
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=NCBBIINEHIPFGJPLBEIFIEBKDIAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=markwiz@us.ibm.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 NNTP newsgroup(s).