Date: Thu, 29 Oct 2015 02:40:52 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> Cc: freebsd-bugs@freebsd.org Subject: Re: [Bug 204049] vmtotal() loading is high when memory utilization is high Message-ID: <20151029014531.V2351@besplex.bde.org> In-Reply-To: <20151028225118.L1832@besplex.bde.org> References: <bug-204049-8@https.bugs.freebsd.org/bugzilla/> <bug-204049-8-MlbJYA75Pk@https.bugs.freebsd.org/bugzilla/> <20151028225118.L1832@besplex.bde.org>
index | next in thread | previous in thread | raw e-mail
On Thu, 29 Oct 2015, Bruce Evans wrote: > ... > There ar many bugs in the implementation of clock_gettime() family. Some > of the related ones are: > - none of the above unportable clock ids is documented > - CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID are bogusly named. > The '_ID' in their name is redundant, and is not used for the name of > any other clock id. It would be useful for them to operated on a general > pid or tid, but they don't. > - the undocumented magic clock ids do act on a general pid or tid. The > thread case is an implementation detail for pthread_getcpuclockid(3) > which is documented. Oops. Actually, CLOCK_VIRTUAL and CLOCK_PROF are documented. Visibility ifdefs and corresponding documentation is broken for most CLOCK ids. CLOCK_PROCESS_CPUTIME_ID and CLOCK_THREAD_CPUTIME_ID are actually standard and undocumented, while CLOCK_VIRTUAL and CLOCK_PROF are nonstandard but documented as standard (by omitting them from the list of documented extensions). The visibility ifdefs are jumbled differently. Brucehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151029014531.V2351>