On Tue, 29 May 2007 11:34:14 +0100 "Matthew Faulkner" <matthew.faulkner@xxxxxxxxx> wrote: > Hey all, > > Not sure if this should be asked within this mailing list or netdev, > so please accept my appologies if it's in the wrong place. > > I'd like to know what the best way to go about "profiling" the linux > networking code is. There are a few different methods of profiling the > linux from applications suchs as OProfile and simply booting the > kernel with the profile=2 option and viewing the /proc/ system, but > i'm not sure which (if any) will do the tasks i require. > Profiling measures the amount of CPU per function by sampling. > Basically I want to profile and find out how long each stage of the > network processing takes, for example, how long the TCP/IP processing > takes (in softIRQ context?) and how long the hardware interupt takes? > etc. Arnaldo (acme) did something with probe insertion that did this. > Thanks for your help > > Matt > - > To unsubscribe from this list: send the line "unsubscribe linux-net" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Stephen Hemminger <shemminger@xxxxxxxxxxxxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
