LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: malc <av1474@comtv.ru>
To: Ingo Molnar <mingo@elte.hu>
Cc: Con Kolivas <kernel@kolivas.org>,
	linux list <linux-kernel@vger.kernel.org>,
	zwane@infradead.org, ck list <ck@vds.kolivas.org>,
	ijuz@mannheim.wgermanyrulez.de,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch] sched: accurate user accounting
Date: Sun, 25 Mar 2007 15:34:48 +0400 (MSD)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703251521270.11555@linmac.oyster.ru> (raw)
In-Reply-To: <20070325075134.GA14453@elte.hu>

On Sun, 25 Mar 2007, Ingo Molnar wrote:

>
> * Con Kolivas <kernel@kolivas.org> wrote:
>
>> For an rsdl 0.33 patched kernel. Comments? Overhead worth it?
>
> we want to do this - and we should do this to the vanilla scheduler
> first and check the results. I've back-merged the patch to before RSDL
> and have tested it - find the patch below. Vale, could you try this
> patch against a 2.6.21-rc4-ish kernel and re-test your testcase?

[..snip..]

Compilation failed with:
kernel/built-in.o(.sched.text+0x564): more undefined references to `__udivdi3' follow

$ gcc --version | head -1
gcc (GCC) 3.4.6

$ cat /proc/cpuinfo | grep cpu
cpu             : 7447A, altivec supported

Can't say i really understand why 64bit arithmetics suddenly became an
issue here.

Am i supposed to run the testcase and see if numbers in `/proc/stat'
now match the reality closer? To be really accurate `/proc/stat'
should be left alone methinks, because no matter how good you try the
fundamential fact that time(and consequently load percentage) is not
really devided in USER_HZ intervals will interfere with ones quest for
accurate statistics. (Wonder what this patch will do to slightly modified
hog that produced this: http://www.boblycat.org/~malc/apc/load-c2d-hog.png
but this will have to wait till i get to the PC at work)

-- 
vale (this is not name/nick/alias, this is latin for farewell)

  parent reply	other threads:[~2007-03-25 11:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-25  1:59 [PATCH] [RFC] " Con Kolivas
2007-03-25  2:14 ` Con Kolivas
2007-03-25  7:51 ` [patch] " Ingo Molnar
2007-03-25  8:39   ` Con Kolivas
2007-03-25  9:04     ` Ingo Molnar
2007-03-25 11:34   ` malc [this message]
2007-03-25 11:46     ` Con Kolivas
2007-03-25 12:02       ` Con Kolivas
2007-03-25 12:32         ` Gene Heskett
2007-03-25 12:41           ` Con Kolivas
2007-03-25 13:33             ` Gene Heskett
2007-03-25 13:05         ` malc
2007-03-25 13:06         ` malc
2007-03-25 14:15           ` Con Kolivas
2007-03-25 14:57             ` malc
2007-03-25 15:08               ` Con Kolivas
2007-03-25 15:19                 ` malc
2007-03-25 15:28                   ` Con Kolivas
2007-03-25 17:14                     ` malc
2007-03-25 23:01                       ` Con Kolivas
2007-03-25 23:57                         ` Con Kolivas
2007-03-26 10:49                           ` malc
2007-03-28 11:37                             ` Ingo Molnar
2007-06-14 17:56                               ` Vassili Karpov
2007-06-14 20:42                                 ` Ingo Molnar
2007-06-14 20:56                                   ` malc
2007-06-14 21:18                                     ` Ingo Molnar
2007-06-14 21:37                                       ` malc
2007-06-15  3:44                                         ` Balbir Singh
2007-06-15  6:07                                           ` malc
2007-06-16 13:21                                             ` Balbir Singh
2007-06-16 14:07                                               ` malc
2007-06-16 18:40                                                 ` Ingo Molnar
2007-06-16 20:31                                                   ` malc
2007-03-26  5:11 Al Boldi
2007-03-26  5:27 ` Mike Galbraith
2007-03-26  8:45 ` Con Kolivas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0703251521270.11555@linmac.oyster.ru \
    --to=av1474@comtv.ru \
    --cc=akpm@linux-foundation.org \
    --cc=ck@vds.kolivas.org \
    --cc=ijuz@mannheim.wgermanyrulez.de \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=zwane@infradead.org \
    --subject='Re: [patch] sched: accurate user accounting' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).