From: Willem Jan Withagen <wjw@digiware.nl>
To: Matt Benjamin <mbenjamin@redhat.com>,
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: Mon, 25 Jan 2016 10:08:46 +0100 [thread overview]
Message-ID: <56A5E61E.80705@digiware.nl> (raw)
In-Reply-To: <20160125000337.GA19230@ultraspiritum.redhat.com>
On 25-1-2016 01:03, Adam C. Emerson wrote:
> On 24/01/2016, Willem Jan Withagen wrote:
>> 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 ??
>
> I had meant that there was an abstraction there, rather than that we had
> CLOCK_MONOTONIC_FAST already. But, does:
>
> https://github.com/ceph/ceph/pull/7340
>
> Work under your system/seem a sane way of doing it?
That is 99,5% of what I had in my WIP.
The difference is that I matched it on __linux__ and __FreeBSD__, but
yours is definitely even better, since it if-then-else on what is really
under observation.
I would comment the last section: the #else with a remark that you
select POSIX if nothing else, but that POSIX is more/unneeded accurate
and slow.
--WjW
next prev parent reply other threads:[~2016-01-25 9:09 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
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 [this message]
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=56A5E61E.80705@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=evelu@redhat.com \
--cc=mbenjamin@redhat.com \
--cc=sweil@redhat.com \
/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.