From: Matt Benjamin <mbenjamin@redhat.com>
To: "Adam C. Emerson" <aemerson@redhat.com>
Cc: Willem Jan Withagen <wjw@digiware.nl>,
Erwan Velu <evelu@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>,
Sage Weil <sweil@redhat.com>
Subject: Re: About ceph_clock_now()
Date: Mon, 25 Jan 2016 15:18:08 -0500 (EST) [thread overview]
Message-ID: <935383330.24835824.1453753088174.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160125201451.GC2818@ultraspiritum.redhat.com>
inline
----- Original Message -----
> From: "Adam C. Emerson" <aemerson@redhat.com>
> To: "Willem Jan Withagen" <wjw@digiware.nl>
> Cc: "Matt Benjamin" <mbenjamin@redhat.com>, "Erwan Velu" <evelu@redhat.com>, "Ceph Development"
> <ceph-devel@vger.kernel.org>, "Sage Weil" <sweil@redhat.com>
> Sent: Monday, January 25, 2016 3:14:51 PM
> Subject: Re: About ceph_clock_now()
>
> On 25/01/2016, Willem Jan Withagen wrote:
> > 1)
> > Currently the code in Adam's looks like:
> > #if defined(CLOCK_MONOTONIC_COARSE)
> > // Linux systems have _COARSE clocks.
> > clock_gettime(CLOCK_MONOTONIC_COARSE, &ts);
> > #elif defined(CLOCK_MONOTONIC_FAST)
> > // BSD systems have _FAST clocks.
> > clock_gettime(CLOCK_MONOTONIC_FAST, &ts);
> > #else
> > // And if we find neither, you may wish to consult your system's
> > // documentation.
> > #warning Falling back to CLOCK_MONOTONIC, may be slow.
> > clock_gettime(CLOCK_MONOTONIC, &ts);
> > #endif
> >
> > And this is repeated in a few more locations.
> > Moreover, it will be required to do that a few times everytime
> > clock_getime is used.
>
> I was originally thinking of just specifying the time constant, but I figured
> that somehow somewhere someone might want to compile on a system without
> clock_gettime. (Windows? I don't know.) Or use the fasttime library or
> something
> where just switching out the constant wouldn't work.
>
> I wouldn't worry about people having to do this every tie they call
> clock_gettime, though, since they really ought to be going through the C++
> Clock
> abstraction. (At least, in the context of the Ceph codebase.)
exactly, this.
>
> --
> 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
>
--
--
Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103
http://www.redhat.com/en/technologies/storage
tel. 734-707-0660
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2016-01-25 20:18 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
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 [this message]
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=935383330.24835824.1453753088174.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=aemerson@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=evelu@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.