News for hackers. Stuff that matters.
Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @02:21PM (#240143)
Why do you insist on making this a flame war? Sit down and write a program that makes 10M trivial system calls (getpid() is a good choice) and one that calls a function to return a constant integer 10M times.

I'm sorry, but you seem to have a wildly inflated idea of the speed of system calls on modern OSs. The real world just doesn't work like that. This is my last post on this thread.

Re:The Greatest Bug of All by spc476 on Wednesday July 09, 2008 @03:04AM (#240874)
I did that a few months ago (http://boston.conman.org/2007/11/30.1) and found some surprising results (http://boston.conman.org/2007/12/02.1)which showed that using getpid() wasn't a good test of system call overhead.
Re:The Greatest Bug of All by tptacek on Wednesday July 09, 2008 @03:21AM (#240888)
That is a really nice catch.
Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @06:49PM (#240471)
By the way, you asked me to time getpid against "a function that returns a constant integer". Obviously that's a silly comparison (getpid isn't really returning a constant; it's a vectored call and it has to pull the PID out of a structure offset from %%fs). But here's a fairer fight: getpid vs. a trivial LFSR:

        s = (s >> 1) ^ (-(s & 1) & 0xd0000001);
I also timed it the way you asked, with wall clock time over 100M iterations (10M runs too fast to time). Surprising even me, getpid wins by almost a full second.

Got another challenge for me to write code for?

Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @04:12PM (#240292)
Here you go:

http://pastie.org/230109

Want the punch line? OSX getpid averages under 100 cycles; snprintf (no IO) averages over 1000.

Re:The Greatest Bug of All by ajross on Tuesday July 08, 2008 @06:58PM (#240480)
Are you sure getpid() is doing a system call and not reading TLS?
Re:The Greatest Bug of All by tptacek on Tuesday July 08, 2008 @07:27PM (#240508)
What a great question! I just checked. Nope:

Breakpoint 1, 0x96210c44 in getpid ()

(gdb) disp/i $eip

2: x/i $eip 0x96210c44 <getpid>: call 0x96210c49 <getpid+5>

(gdb) stepi

0x96210c49 in getpid ()

2: x/i $eip 0x96210c49 <getpid+5>: pop %ecx

0x96210c4a in getpid ()

2: x/i $eip 0x96210c4a <getpid+6>: lea 0xa6427a3(%ecx),%ecx

0x96210c50 in getpid ()

2: x/i $eip 0x96210c50 <getpid+12>: mov (%ecx),%eax

0x96210c52 in getpid ()

2: x/i $eip 0x96210c52 <getpid+14>: test %eax,%eax

0x96210c54 in getpid ()

2: x/i $eip 0x96210c54 <getpid+16>: jle 0x96210c57 <getpid+19>

0x96210c57 in getpid () 2: x/i $eip 0x96210c57 <getpid+19>: mov $0x14,%eax

0x96210c5c in getpid ()

2: x/i $eip 0x96210c5c <getpid+24>: call 0x961e8cf4 <_sysenter_trap>