On Fri, Jan 23, 2015 at 2:18 PM, Davide Italiano wrote:
> On Fri, Jan 23, 2015 at 12:56 PM, Will Andrews wrote:
>> On Fri, Jan 23, 2015 at 11:23:57AM -0800, Davide Italiano wrote:
>>> What's the rationale behind this change?
>>
>> The rationale was to match the clock used to the name (and implied
On Fri, Jan 23, 2015 at 12:56 PM, Will Andrews wrote:
> On Fri, Jan 23, 2015 at 11:23:57AM -0800, Davide Italiano wrote:
>> What's the rationale behind this change?
>
> The rationale was to match the clock used to the name (and implied intent)
> of the variables used to store/manipulate the data.
On Fri, 2015-01-23 at 13:56 -0700, Will Andrews wrote:
> On Fri, Jan 23, 2015 at 11:23:57AM -0800, Davide Italiano wrote:
> > What's the rationale behind this change?
>
> The rationale was to match the clock used to the name (and implied intent)
> of the variables used to store/manipulate the data
On Fri, Jan 23, 2015 at 11:23:57AM -0800, Davide Italiano wrote:
> What's the rationale behind this change?
The rationale was to match the clock used to the name (and implied intent)
of the variables used to store/manipulate the data.
It's possible that 'uptime' is entirely the wrong term in vmst
On Fri, Jan 23, 2015 at 8:18 AM, Will Andrews wrote:
> Author: will
> Date: Fri Jan 23 16:18:39 2015
> New Revision: 277570
> URL: https://svnweb.freebsd.org/changeset/base/277570
>
> Log:
> Use CLOCK_UPTIME to get the uptime instead of CLOCK_MONOTONIC.
>
> Submitted by: asomers
> MFC after:
Author: will
Date: Fri Jan 23 16:18:39 2015
New Revision: 277570
URL: https://svnweb.freebsd.org/changeset/base/277570
Log:
Use CLOCK_UPTIME to get the uptime instead of CLOCK_MONOTONIC.
Submitted by: asomers
MFC after:1 week
Sponsored by: Spectra Logic
MFSpectraBSD: 1066740 on 20
