Date: Thu, 20 Aug 2015 11:10:32 -0400 From: Ryan Stone <rysto32@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: vm_lowmem is prevented every 2**31 ticks Message-ID: <CAFMmRNwxc9zZt0frdh4W72M7_JG-BxQu1u3gQdaP-t4Mck0Xzg@mail.gmail.com> In-Reply-To: <1438819170.70393.227.camel@freebsd.org> References: <CAFMmRNwKd7FpQBdG5C=yynSAN9o59pD-ERhZ5Z0BMykbg_Yy8Q@mail.gmail.com> <1438819170.70393.227.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 5, 2015 at 7:59 PM, Ian Lepore <ian@freebsd.org> wrote: > If you're measuring elapsed time, please use getbinuptime() rather than > the time of day clock (which can be stepped arbitrarily). > > Hey wait a sec... if it's currently some_ticks/hz it's counting seconds, > right? So no need to mess with bintimes, if whole seconds are good > enough just use the global time_uptime. > i thought that there was such a variable, but a quick search didn't turn it up. Thanks. (And thanks for also catching my potential mistake in not using uptime -- that would have been embarrassing) I've put the potential fix up for review here: https://reviews.freebsd.org/D3439
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwxc9zZt0frdh4W72M7_JG-BxQu1u3gQdaP-t4Mck0Xzg>