On 24-1-2016 12:53, Willem Jan Withagen wrote: > On 23-1-2016 22:55, Adam C. Emerson wrote: >> On 23/01/2016, Matt Benjamin wrote: >>> Hi Willem, >>> >>> Agree. The c++ notations and our declarations using them do centralize all this. I don't know if we're actually defining anything equivalent to the coarse/fast clocks (it seems like a good idea, and I assumed we would), and it's straightforward to do. >>> >>> (Adam may have, already.) >> >> We do. We can switch out ceph::coarse_mono_clock for BSD's FAST MONO CLOCK or on >> systems that don't have a coarse/fast option, just fall back to CLOCK_MONOTONIC >> easily. >> > Cool, > > Last time I tried a testrun after catching up to HEAD, I got quite a few > compiletime errors. > Guess I've got to catch up again. Not to irritate, but I just updated my copy of ceph:master and I could not find any trace of a reference to CLOCK_MONOTONIC_FAST, so it has to be in any of the WIPs ?? --WjW -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
