next up previous contents
Next: Pretty-printing traces Up: Simulation output Previous: Simulation output   Contents


Raw tcsim output

tcsim prints tracing information on standard output. Each line has the following format:

time event : $\ldots$

time
The simulation time at which the even has occurred, either in seconds or in jiffies.
event
The event type. Currently, the following events are reported:

I ingress queuing discipline
E device enqueue
D device dequeue
T execution of a tc command
* error or diagnostic

Additionally, if function call tracing is enabled (with -v), the following events are reported:

c call to classifier
i call to enqueue function of the ingress queuing discipline
e call to enqueue function of an egress queuing discipline
d call to dequeue function
r call to requeue function
x call to drop function
s call to reshape_fail callback
p call to tcf_police

For device enqueue and dequeue events, the following additional information is printed:

skb_addr length : device: content $\ldots$

skb_addr
The address of the skb.
length
Length of the packet.
content
Packet content, printed in groups of four hex bytes. The length can be limited with the -s option. If bytes were not displayed due to -s, tcsim ends the line with three dots (...)

For tc command execution, the command line (including the tc command) is printed.

For all tracing events, the following information is printed:

skb_addr length : $<$level$>$ descr $\ldots$

skb_addr
Address of the skb, 0x0 if no skb is available
length
Length of the packet, 0 if no skb is available
level
Call depth (enclosed by <>), starting at zero.
descr
Description of the event, usually including the kind and ID of the element, and the return value of the function


next up previous contents
Next: Pretty-printing traces Up: Simulation output Previous: Simulation output   Contents
Martin A. Brown 2003-11-06