From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Sage Weil <sage@inktank.com>
Cc: Alex Elder <elder@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH 2/2] libceph: validate timespec conversions
Date: Mon, 22 Apr 2013 12:12:03 -0400 (EDT) [thread overview]
Message-ID: <2011602102.65.1366647123451.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1304220907140.15710@cobra.newdream.net>
I was thinking about the seconds component.
----- "Sage Weil" <sage@inktank.com> wrote:
> On Mon, 22 Apr 2013, Matt W. Benjamin wrote:
> >
> > ----- "Alex Elder" <elder@inktank.com> wrote:
> >
> > > A ceph timespec contains 32-bit unsigned values for its seconds
> and
> > > nanoseconds components. For a standard timespec, both fields are
> > > signed, and the seconds field is almost surely 64 bits.
> >
> > Is the Ceph timespec going to change at some point?
>
> I don't think so. 32-bits is enough for the billion nanoseconds in a
>
> second. And I'm not sure if the signedness is used/useful... the ceph
>
> utime_t code always normalizes the ns result to be in [0, 1 billion).
>
> sage
--
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI 48104
http://linuxbox.com
tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309
next prev parent reply other threads:[~2013-04-22 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-21 21:12 [PATCH 0/2] libceph: odds and ends Alex Elder
2013-04-21 21:12 ` [PATCH 1/2] libceph: add signed type limits Alex Elder
2013-04-21 21:14 ` Alex Elder
2013-04-22 22:55 ` Josh Durgin
2013-04-21 21:15 ` [PATCH 2/2] libceph: validate timespec conversions Alex Elder
2013-04-22 15:00 ` Matt W. Benjamin
2013-04-22 16:08 ` Sage Weil
2013-04-22 16:12 ` Matt W. Benjamin [this message]
2013-04-22 16:22 ` Sage Weil
2013-04-22 16:25 ` Alex Elder
2013-04-22 22:57 ` Josh Durgin
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=2011602102.65.1366647123451.JavaMail.root@thunderbeast.private.linuxbox.com \
--to=matt@linuxbox.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.com \
--cc=sage@inktank.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.