linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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 07:46:39 -0700	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFOEBLDIAA.acurtis@onz.com> (raw)
In-Reply-To: <OF93B8F461.B08FA3A3-ON85256BCE.004FA168@raleigh.ibm.com>


> KGDB may be a good start. netif_rx() is where the packet gets
> passed to the
> stack. It basically throws the packet on a linklist for ip_rcv() in
> ip_input.c to pick up and start processing it through the stack until it
> passes the results to the application. This is tough stuff. Let
> me know how
> you make out.

Any idea who the network stack maintainer is? Perhaps they have something
that timestamps a packets progress through the pipeline.

> I would guess the IP stack has not changed much between kernels.
> I would be
> more concerned about how the scheduler is working and other kernel tasks.

The system is basically idle except for the NFS/FTP traffic.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-04 14:46 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 [this message]
2002-06-04 15:05   ` Michael Fischer
  -- 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=NCBBIINEHIPFGJPLBEIFOEBLDIAA.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).