From owner-freebsd-bugs@freebsd.org  Wed Oct 28 15:41:03 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E9BCA20EA3
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 28 Oct 2015 15:41:03 +0000 (UTC)
 (envelope-from brde@optusnet.com.au)
Received: from mail105.syd.optusnet.com.au (mail105.syd.optusnet.com.au
 [211.29.132.249])
 by mx1.freebsd.org (Postfix) with ESMTP id D682914C7
 for <freebsd-bugs@freebsd.org>; Wed, 28 Oct 2015 15:41:02 +0000 (UTC)
 (envelope-from brde@optusnet.com.au)
Received: from c211-30-166-197.carlnfd1.nsw.optusnet.com.au
 (c211-30-166-197.carlnfd1.nsw.optusnet.com.au [211.30.166.197])
 by mail105.syd.optusnet.com.au (Postfix) with ESMTPS id 66E9510479D1
 for <freebsd-bugs@freebsd.org>; Thu, 29 Oct 2015 02:40:52 +1100 (AEDT)
Date: Thu, 29 Oct 2015 02:40:52 +1100 (EST)
From: Bruce Evans <brde@optusnet.com.au>
X-X-Sender: bde@besplex.bde.org
cc: freebsd-bugs@freebsd.org
Subject: Re: [Bug 204049] vmtotal() loading is high when memory utilization
 is high
In-Reply-To: <20151028225118.L1832@besplex.bde.org>
Message-ID: <20151029014531.V2351@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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Optus-CM-Score: 0
X-Optus-CM-Analysis: v=2.1 cv=R4L+YolX c=1 sm=1 tr=0
 a=KA6XNC2GZCFrdESI5ZmdjQ==:117 a=PO7r1zJSAAAA:8 a=9cW_t1CCXrUA:10
 a=JzwRw_2MAAAA:8 a=kj9zAlcOel0A:10 a=tnlmPoUn9fLxoWFsF6EA:9
 a=CjuIK1q_8ugA:10
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2015 15:41:03 -0000

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.

Bruce