[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703251705160.7018@linmac.oyster.ru>
Date: Sun, 25 Mar 2007 17:06:38 +0400 (MSD)
From: malc <av1474@...tv.ru>
To: Con Kolivas <kernel@...ivas.org>
cc: Ingo Molnar <mingo@...e.hu>,
linux list <linux-kernel@...r.kernel.org>, zwane@...radead.org,
ck list <ck@....kolivas.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [patch] sched: accurate user accounting
On Sun, 25 Mar 2007, Con Kolivas wrote:
> On Sunday 25 March 2007 21:46, Con Kolivas wrote:
>> On Sunday 25 March 2007 21:34, malc wrote:
>>> On Sun, 25 Mar 2007, Ingo Molnar wrote:
>>>> * Con Kolivas <kernel@...ivas.org> wrote:
>>>>> For an rsdl 0.33 patched kernel. Comments? Overhead worth it?
[..snip..]
>
> ---
> Currently we only do cpu accounting to userspace based on what is
> actually happening precisely on each tick. The accuracy of that
> accounting gets progressively worse the lower HZ is. As we already keep
> accounting of nanosecond resolution we can accurately track user cpu,
> nice cpu and idle cpu if we move the accounting to update_cpu_clock with
> a nanosecond cpu_usage_stat entry. This increases overhead slightly but
> avoids the problem of tick aliasing errors making accounting unreliable.
>
> Signed-off-by: Con Kolivas <kernel@...ivas.org>
> Signed-off-by: Ingo Molnar <mingo@...e.hu>
[..snip..]
Forgot to mention. Given that this goes into the kernel, shouldn't
Documentation/cpu-load.txt be amended/removed?
--
vale
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists