Changeset 381fc99 in rtems


Ignore:
Timestamp:
Feb 9, 1999, 8:30:34 PM (20 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, master
Children:
ba0bd42
Parents:
5bb77c4
Message:

Added information on debug modes that can be enabled in the network stack.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/networking/testing.t

    r5bb77c4 r381fc99  
    4646@item Performance measurements are not impacted by other systems on
    4747the network.
     48
     49@end itemize
     50
     51@section Debug Output
     52
     53There are a number of sources of debug output that can be enabled
     54to aid in tracing the behavior of the network stack.  The following
     55is a list of them:
     56
     57@itemize @bullet
     58
     59@item mbuf activity
     60
     61There are commented out calls to @code{printf} in the file
     62@code{sys/mbuf.h} in the network stack code.  Uncommenting
     63these lines results in output when mbuf's are allocated
     64and freed.  This is very useful for findind memory leaks.
     65
     66@item TX and RX queuing
     67
     68There are commented out calls to @code{printf} in the file
     69@code{net/if.h} in the network stack code.  Uncommenting
     70these lines results in output when packets are placed
     71on or removed from one of the transmit or receive packet
     72queues.  These queues can be viewed as the boundary line
     73between a device driver and the network stack.  If the
     74network stack is enqueuing packets to be transmitted that
     75the device driver is not dequeuing, then that is indicative
     76of a problem in the transmit side of the device driver.
     77Conversely, if the device driver is enqueueing packets
     78as it receives them (via a call to @code{ether_input}) and
     79they are not being dequeued by the network stack,
     80then there is a problem.  This situation would likely indicate
     81that the network server task is not running.
     82
     83@item TCP state transitions
     84
     85In the unlikely event that one would actually want to see
     86TCP state transitions, the @code{TCPDEBUG} macro can be defined
     87in the file @code{opt_tcpdebug.h}.  This results in the routine
     88@code{tcp_trace()} being called by the network stack and
     89the state transitions logged into the @code{tcp_debug} data
     90structure.  If the variable @code{tcpconsdebug} in the file
     91@code{netinet/tcp_debug.c} is set to 1, then the state transitions
     92will also be printed to the console.
    4893
    4994@end itemize
Note: See TracChangeset for help on using the changeset viewer.