>I just saw with truss the following: >fstat64(5, 0x08062448) = 0 >fcntl(5, F_SETFD, 0x00000001) = 0 >llseek(5, 1068220, SEEK_SET) = 1068220 >fstat64(5, 0x080452C0) = 0 >fstat64(5, 0x080451D0) = 0 >ioctl(5, TCGETA, 0x08045270) Err#25 ENOTTY >read(5, " F r o m k d e - b u g".., 131072) = 131072 >llseek(5, 0xFFFFFFFFFFFE0831, SEEK_CUR) = 1070317 >close(5) = 0 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 >time() = 1281441644 > >If I understand it correctly the call of time() is a system call and requires >each time context switching etc...
There's a fast-trap implementation for gettimeofday(). Why are they running time() in a loop? Perhaps it's better to first implement time() as a wrapper round gettimeofday() and see if that changes the performance/ But if you call time() in a loop, then even the best performance won't change the runtime: it will just call time() more times. Casper _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
