Hello,
Roland McGrath, le Tue 11 Jun 2013 16:13:53 -0700, a écrit :
> > Basically, top doesn't report correct CPU times. This is caused by
> > sysconf() returning 100 while values read from /proc are true tick
> > counts, hence 100 per second at most.
>
> In fact, that is not a "true tick cou
On Tue, Jun 11, 2013 at 04:13:53PM -0700, Roland McGrath wrote:
> > Basically, top doesn't report correct CPU times. This is caused by
> > sysconf() returning 100 while values read from /proc are true tick
> > counts, hence 100 per second at most.
>
> In fact, that is not a "true tick count".
> Basically, top doesn't report correct CPU times. This is caused by
> sysconf() returning 100 while values read from /proc are true tick
> counts, hence 100 per second at most.
In fact, that is not a "true tick count". Most modern Linux kernels have
ticks at 1024Hz, for example. The ABI for
On Tue, Jun 11, 2013 at 03:55:46PM -0700, Roland McGrath wrote:
> > The /proc file system is merely an example. Also, it's not internal to
> > libc, since it gets exported through sysconf(_SC_CLK_TCK).
>
> You'll have to explain what problem you think there is more thoroughly.
Basically, top does
> The /proc file system is merely an example. Also, it's not internal to
> libc, since it gets exported through sysconf(_SC_CLK_TCK).
You'll have to explain what problem you think there is more thoroughly.
On Tue, Jun 11, 2013 at 03:49:17PM -0700, Roland McGrath wrote:
> This change doesn't make any sense to me. The explanation refers to /proc,
> which is wholly irrelevant to libc internals.
The /proc file system is merely an example. Also, it's not internal to
libc, since it gets exported through
This change doesn't make any sense to me. The explanation refers to /proc,
which is wholly irrelevant to libc internals.
- Forwarded message from Richard Braun -
Date: Mon, 6 May 2013 21:49:56 +0200
From: Richard Braun
To: bug-hurd@gnu.org
Subject: [PATCH] Make __getclktck return 100 for the Hurd
X-Mailer: git-send-email 1.7.2.5
While it's true that Mach time values are returned in microseconds, they
are
