On Fri, Feb 25, 2011 at 8:22 PM, Mauro Romano Trajber <trajber@xxxxxxxxx> wrote: > Thanks Enrico and Daniel, you're right. glibc was caching getpid(); but this > is not the root cause of this behavior. > Going further, I decide to use call getpid without glibc, using > syscall(SYS_getpid) to test this behavior and it happened again. > Calling it once, the test consumes about 7k CPU cycles and 10 calls consumes > about 10k CPU cycles. > Any ideas ? Can you post a pointer to your code and information about how you got this numbers? thanks, Daniel. _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
