Nick Piggin wrote:
Andrew Theurer wrote:
Nick, can you describe the system you run the DB tests on? Do you
have any cpu idle time stats and hopefully some context switch rate
stats?
Yeah, it is dbt3-pgsql on OSDL's 8-way STP machines. I think they're
PIII Xeons with 2MB L2 cache.
I had been hav
Andrew Theurer wrote:
Nick, can you describe the system you run the DB tests on? Do you have
any cpu idle time stats and hopefully some context switch rate stats?
Yeah, it is dbt3-pgsql on OSDL's 8-way STP machines. I think they're
PIII Xeons with 2MB L2 cache.
I had been having some difficulty r
Nick, can you describe the system you run the DB tests on? Do you have
any cpu idle time stats and hopefully some context switch rate stats?
I think I understand the concern [patch 6] of stealing a task from one
node to an idle cpu in another node, but I wonder if we can have some
sort of che
; >
>
> Yes. Which might also explain why I didn't see -ve intervals :( Thanks
> Ingo.
>
> In the context of the whole patchset, testing has mainly been based
> around multiprocessor behaviour so this doesn't invalidate that.
nono, by 'this' i only meant that pa
On Thu, 2005-02-24 at 08:46 +0100, Ingo Molnar wrote:
> * Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > 1/13
> >
>
> ugh, has this been tested? It needs the patch below.
>
Yes. Which might also explain why I didn't see -ve intervals :(
Thanks Ingo.
In the context of the whole patchset, testing
* Nick Piggin <[EMAIL PROTECTED]> wrote:
> 1/13
>
ugh, has this been tested? It needs the patch below.
Ingo
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
--- linux/kernel/sched.c.orig
+++ linux/kernel/sched.c
@@ -2704,11 +2704,11 @@ need_resched_nonpreemptible:
schedstat_i
1/13
Some fixes for unsynchronised TSCs. A task's timestamp may have been set
by another CPU. Although we try to adjust this correctly with the
timestamp_last_tick field, there is no guarantee this will be exactly right.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/kernel/sche
7 matches
Mail list logo
