I seriously doubt that people really care _that_ much about a
precise time source for aio timeouts, and we should spend more
time on making it efficient and easy to use than on worrying about
the precision. People who do care can fall back to gettimeofday()
and try to correct for it that way.
In that case define the time to be approximate and nothing more.
The reason for the original suggestion was it seem feasible in the
future the syscall could be used for other purposes (multimedia
synchornisation) *and* be of value if made more precise without adding
yet another syscall at a later stage to do just this.
--cw
-
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/