From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Adam C. Emerson" Subject: Re: About ceph_clock_now() Date: Sat, 23 Jan 2016 16:55:44 -0500 Message-ID: <20160123215543.GA8011@ultraspiritum.redhat.com> References: <177186823.10053087.1452614184109.JavaMail.zimbra@redhat.com> <964746730.10566211.1452681675142.JavaMail.zimbra@redhat.com> <1365711662.13730117.1453220271917.JavaMail.zimbra@redhat.com> <20160119162902.GA21358@ultraspiritum.redhat.com> <1522288191.15295456.1453404176015.JavaMail.zimbra@redhat.com> <1575597139.15885899.1453478438366.JavaMail.zimbra@redhat.com> <56A368C1.8000508@digiware.nl> <747915460.23855157.1453580447803.JavaMail.zimbra@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58483 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753276AbcAWVzq (ORCPT ); Sat, 23 Jan 2016 16:55:46 -0500 Content-Disposition: inline In-Reply-To: <747915460.23855157.1453580447803.JavaMail.zimbra@redhat.com> Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Matt Benjamin Cc: Willem Jan Withagen , Erwan Velu , Sage Weil , The Sacred Order of the Squid Cybernetic 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. -- Senior Software Engineer Red Hat Storage, Ann Arbor, MI, US IRC: Aemerson@{RedHat, OFTC, Freenode} 0x80F7544B90EDBFB9 E707 86BA 0C1B 62CC 152C 7C12 80F7 544B 90ED BFB9