> Why do we need this? > > Correctness: ... > Consolidation: ...
Any performance measurements? ia64 has gone to some lengths to ensure that gettimeofday(2) has a very low overhead (it does show up in the kernel profiles of some benchmarks ... managed runtime systems in particular, but others like to get timestamps at quite frighteningly short intervals). So I'm interested in smp cases where are moderate number of cpus (4-16) are pounding on gettimeofday(). I think that the huge SMP systems running HPC workloads spend less of their time asking what time it is, so I'm not as worried about the 512 cpu ... but if all 512 cpus do happen to call gettimeofday() at the same time the system shouldn't sink into the swamp as cache-lines bounce around. -Tony - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
