From: "Adam C. Emerson" <aemerson@redhat.com>
To: Matt Benjamin <mbenjamin@redhat.com>
Cc: Willem Jan Withagen <wjw@digiware.nl>,
Erwan Velu <evelu@redhat.com>, Sage Weil <sweil@redhat.com>,
The Sacred Order of the Squid Cybernetic
<ceph-devel@vger.kernel.org>
Subject: Re: About ceph_clock_now()
Date: Sat, 23 Jan 2016 16:55:44 -0500 [thread overview]
Message-ID: <20160123215543.GA8011@ultraspiritum.redhat.com> (raw)
In-Reply-To: <747915460.23855157.1453580447803.JavaMail.zimbra@redhat.com>
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
next prev parent reply other threads:[~2016-01-23 21:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177186823.10053087.1452614184109.JavaMail.zimbra@redhat.com>
2016-01-12 15:59 ` About ceph_clock_now() Erwan Velu
2016-01-12 17:32 ` Adam C. Emerson
2016-01-13 10:41 ` Erwan Velu
2016-01-13 13:48 ` Sage Weil
2016-01-13 14:52 ` Matt Benjamin
2016-01-14 16:10 ` Erwan Velu
2016-01-14 16:14 ` Adam C. Emerson
2016-01-19 16:17 ` Erwan Velu
2016-01-19 16:29 ` Adam C. Emerson
2016-01-19 16:57 ` Erwan Velu
2016-01-21 19:22 ` Erwan Velu
2016-01-22 16:00 ` Erwan Velu
2016-01-22 17:35 ` Adam C. Emerson
2016-01-26 14:12 ` Erwan Velu
2016-01-23 11:49 ` Willem Jan Withagen
2016-01-23 20:20 ` Matt Benjamin
2016-01-23 21:55 ` Adam C. Emerson [this message]
2016-01-24 11:53 ` Willem Jan Withagen
2016-01-24 12:51 ` Willem Jan Withagen
2016-01-25 0:03 ` Adam C. Emerson
2016-01-25 9:08 ` Willem Jan Withagen
2016-01-25 9:58 ` Erwan Velu
2016-01-25 10:57 ` Willem Jan Withagen
2016-01-25 17:22 ` Adam C. Emerson
[not found] ` <56A66099.4030501@digiware.nl>
[not found] ` <1523354716.24670379.1453744826329.JavaMail.zimbra@redhat.com>
2016-01-25 19:38 ` Willem Jan Withagen
2016-01-25 20:14 ` Adam C. Emerson
2016-01-25 20:18 ` Matt Benjamin
2016-01-25 20:22 ` Willem Jan Withagen
2016-01-13 15:28 ` Adam C. Emerson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160123215543.GA8011@ultraspiritum.redhat.com \
--to=aemerson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=evelu@redhat.com \
--cc=mbenjamin@redhat.com \
--cc=sweil@redhat.com \
--cc=wjw@digiware.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.