> > I believe you need it system-global. If task A tells task B "its
> > 10:30:00" and than task B does gettimeofday and gets "10:29:59", it
> > will be confused for sure.
> Hence the requirement that it be monotonically increasing.
Processes expecting time to increase strictly monotonically across process
boundaries will enjoy life in cluster settings or when the admin adjusts the
time.
In short, those programs are already broken.
Of course, physically that should be true, Star Trek or not ;), but it is a
really hard promise to keep across multiple nodes (think Mosix, CC/NC-NUMA or
even real clusters which distributed processing).
Serializing all gettimeofday() calls via a single counter at least is a rather
bad idea.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
-- Principal Squirrel SuSE Labs - Research & Development, SuSE Linux AG "If anything can go wrong, it will." "Chance favors the prepared (mind)." -- Capt. Edward A. Murphy -- Louis Pasteur - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/