Data networking devices typically include line interfaces, aggregators, queuing engines, a scheduler, packet memory, look-up engines, and a packet processor. The packet processor generally includes modules that perform various processing functions. For example, parsing a packet, classifying a packet, determining Internet Protocol (IP) routing, editing, address look-up, etc. At present, these packet processors operate at very high speeds and are densely pipelined with a throughput of about a packet per clock cycle.
Referring to
Trace trigger 14 compares incoming packets with a set of trace parameters, and, if appropriate, sends a trigger signal to the tracer devices 22a-22c to monitor the processing stages 26a-26c).
In one example, a trace trigger includes a data control register (not shown), a data comparator (not shown) and a mask register (not shown) to specify the trace parameters. Determining if the trace parameters are in an incoming packet is performed using a masked comparison or masked matching on relevant portions of the incoming packet header for example.
Application 30 may be any application that benefits from packet tracing, for example, a central processing unit, a device driver, a protocol stack, debugging software, a software program and the like. Application 30 provides the trace parameters to the trace trigger to indicate which types of packets to trace.
Each tracer device 22a-22c includes a register (e.g., register 24a, register 24b and register 24c). Each tracer device 22a-22c monitors packets within a corresponding processing stage (e.g., tracer device 22a monitors processing stage 26a, tracer device 22b monitors processing stage 26b, and tracer device 22c monitors processing stage 26c). Monitoring a packet within a processing stage includes determining what processing was done on the packet, how the processing was performed, how the packet was modified during processing and the like. In one example, trace devices 22a-22c are dedicated hardware that collect information when enabled by a trigger signal (e.g., a flag) from the trace trigger 14.
Trace trigger 14 determines if a packet will be traced as the packet passes through each of the processing stages 26a-26c within packet processor 18 and, if it does, sends the trigger signal to the tracer devices 22a-22c to monitor the packet's progress. In one example, the trigger signal is sent to each of the trace devices 22a-22c serially and follows the packet in parallel through each tracer device 22a-22c corresponding to the processing stage 26a-26c where the packet is being processed. In this configuration, each processing stage may be processing a different packet simultaneously and whether a packet is being traced at a particular stage is distinguishable by the tracing signal received at the respective tracer device.
Each tracer device 22a-22c stores within its respective register 24a-24c an indication. The indication may denote one or more of the following: whether the packet has passed through its corresponding processing stage, what processing was performed, how the packet was modified and so forth.
Using system 10, application 30 can monitor designated packets as they pass through the various processing stages within the packet processor 18 by reading the registers 26a-26c within the tracer devices 22a-22c.
Referring to
Process 50 receives (53) a packet. For example, the packet is received by processor 18 and by trace trigger 14 from a network. Process determines (55) if the packet has the trace trigger parameters. For example, trace trigger 14 analyzes the packet and determines if the packet contains the trace trigger parameter, for example, an IP source address in the header. If the packet does contain the trace trigger parameters, process 50 sends (57) a trigger signal to the tracer devices 22a-22c indicating that the packet will be traced. For example, the trigger signal is sent to trace device 22a. After processing stage 26a completes processing of the packet, the trace signal is sent to tracer device 22b and after processing stage 26b completes processing of the packet, the tracer signal is sent to tracer device 22c.
Process 50 monitors (59) a packet has at each processing stage. For example, each tracer device 22a-22c monitors its corresponding processing stage 26a-26c to determine if the packet completes the processing stage, what modifications were made to the packet, what processing was performed and so forth.
When the packet passes through a processing stage, process 50 stores (61) an indication that the packet is through the processing stage, what modifications were made at that processing stage, what processing was performed and so forth. For example, tracer device 22a-22d stores the indication at its register 24a-24c.
Process 50 sends (62) a notification to application 30 that the processing is complete. Process 50 sends (63) the indication from each register 24a-24c to application 30.
Packet tracing system 10 aids in device drive and protocol stack development. Without packet tracing system 10, developers would depend on a packet processor's external behavior to determine the status of the packet processing within a silicon device. Sometimes special probes would be used, which can connect to a logic analyzer externally. Such solutions are expensive and time-consuming to set-up.
Packet tracing system 10 is a cost effective way to monitor and record the packet processing in real-time. Since trace indications are stored in registers, reading and analyzing the data is not time critical. Designating the trace trigger parameters enables a user to pinpoint a packet out of a large number of packets. Packet tracing system 10 may also be used during silicon debugging or circuit emulations.
Process 50 is not limited to use with the hardware and software of
Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs can be implemented in assembly or machine language. The language may be a compiled or an interpreted language. Each computer program may be stored on a storage medium or device e.g., CD-ROM, hard disk, or magnetic diskette that is readable by a general or special purpose programmable computer for configuring and operating the computer when the storage medium or device is read by the computer to perform process 50. Process 50 may also be implemented as one or more machine-readable storage media, configured with a computer program(s), where upon execution, instructions in the computer program(s cause a computer to operate in accordance with process 50.
Referring to
The process described herein is not limited to the specific embodiments described herein. For example, the process described herein is not limited to the specific processing order of
In some examples, the trigger signal may be a flag.
In some examples, the trigger signal is sent to each tracer device 22a-22c simultaneously. Each trace device 22a-22c delays tracing the packet to correspond to the arrival of the packet at the tracer device's respective processing stage.
In some examples, the trace trigger may be configurable for a “one time trace mode” or an “auto repeat mode”. In the “auto repeat mode”, a counter may be used to indicate the number of times packets were traced.
In other examples, the tracer device is positioned within its corresponding processing stage. In other examples, the trace trigger is positioned within the processor.
Other embodiments not described herein are also within the scope of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5012947 | Roland | May 1991 | A |
5333320 | Seki | Jul 1994 | A |
5511215 | Terasaka et al. | Apr 1996 | A |
5598410 | Stone | Jan 1997 | A |
5648965 | Thadani et al. | Jul 1997 | A |
5678060 | Yokoyama et al. | Oct 1997 | A |
5781549 | Dai | Jul 1998 | A |
5802065 | Ogawa et al. | Sep 1998 | A |
5848290 | Yoshida et al. | Dec 1998 | A |
6338078 | Chang et al. | Jan 2002 | B1 |
6463067 | Hebb et al. | Oct 2002 | B1 |
6526500 | Yumoto et al. | Feb 2003 | B1 |
6654823 | Soejima et al. | Nov 2003 | B2 |
6732253 | Redford | May 2004 | B1 |
6778534 | Tal et al. | Aug 2004 | B1 |
6804240 | Shirakawa et al. | Oct 2004 | B1 |
6954789 | Dietz et al. | Oct 2005 | B2 |
6957272 | Tallegas et al. | Oct 2005 | B2 |
7075926 | Cathey et al. | Jul 2006 | B2 |
7164698 | Krishnamurthi et al. | Jan 2007 | B1 |
7181742 | Hooper | Feb 2007 | B2 |
7190695 | Schaub et al. | Mar 2007 | B2 |
7228348 | Farley et al. | Jun 2007 | B1 |
7304999 | Sukonik et al. | Dec 2007 | B2 |
7313142 | Matsuo et al. | Dec 2007 | B2 |
7418536 | Leung et al. | Aug 2008 | B2 |
7424019 | Kopelman et al. | Sep 2008 | B1 |
7502375 | Hahn et al. | Mar 2009 | B2 |
20020054594 | Hoof et al. | May 2002 | A1 |
20020071433 | Tsuruoka et al. | Jun 2002 | A1 |
20020085560 | Cathey et al. | Jul 2002 | A1 |
20020120828 | Modelski et al. | Aug 2002 | A1 |
20030046429 | Sonksen | Mar 2003 | A1 |
20030212840 | Namba | Nov 2003 | A1 |
20030231634 | Henderson et al. | Dec 2003 | A1 |
20040085906 | Ohtani et al. | May 2004 | A1 |
20040190512 | Schultz | Sep 2004 | A1 |
Number | Date | Country | |
---|---|---|---|
20050149604 A1 | Jul 2005 | US |