One way would be to use: CycleCountAccum <http://www.read.cs.ucla.edu/click/elements/cyclecountaccum> collects differences in cycle counters PerfCountAccum<http://www.read.cs.ucla.edu/click/elements/perfcountaccum> collects differences in Pentium Pro performance metrics PerfCountInfo<http://www.read.cs.ucla.edu/click/elements/perfcountinfo> turn on Pentium Pro performance metrics RoundTripCycleCount<http://www.read.cs.ucla.edu/click/elements/roundtripcyclecount> measures round trip cycles on a push or pull path SetCycleCount<http://www.read.cs.ucla.edu/click/elements/setcyclecount> stores cycle count in annotation SetPerfCount<http://www.read.cs.ucla.edu/click/elements/setperfcount> stores Pentium Pro performance metric in annotation See http://www.read.cs.ucla.edu/click/elements#counters
These are only available in the linuxmodule package. On 10/23/07, Archit Gupta <[EMAIL PROTECTED]> wrote: > > Hi, > > I have written an element which processes every packet. I would now > like to profile the performance of the element. I suppose gprof would > be useful here. I would be interested in knowing what tools/techniques > people use to profile their elements/code. > > Thanks, > > Archit > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
