LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xenofon Antidides <xantidides@yahoo.gr>
To: Ingo Molnar <mingo@elte.hu>, Con Kolivas <kernel@kolivas.org>
Cc: linux list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [test] hackbench.c interactivity results: vanilla versus SD/RSDL
Date: Fri, 30 Mar 2007 15:05:13 +0000 (GMT) [thread overview]
Message-ID: <325618.89505.qm@web26701.mail.ukl.yahoo.com> (raw)
----- Original Message ----
From: Ingo Molnar <mingo@elte.hu>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux list <linux-kernel@vger.kernel.org>; Andrew Morton <akpm@linux-foundation.org>; Mike Galbraith <efault@gmx.de>
Sent: Thursday, March 29, 2007 9:22:49 PM
Subject: [test] hackbench.c interactivity results: vanilla versus SD/RSDL
* Ingo Molnar <mingo@elte.hu> wrote:
> * Con Kolivas <kernel@kolivas.org> wrote:
>
> > I'm cautiously optimistic that we're at the thin edge of the bugfix
> > wedge now.
[...]
> and the numbers he posted:
>
> http://marc.info/?l=linux-kernel&m=117448900626028&w=2
We been staring at these numbers for while now and we come to the conclusion they wrong.
The test is f is 3 tasks, two on different and one on same cpu as sh here:
virgin 2.6.21-rc3-rsdl-smp
top - 13:52:50 up 7 min, 12 users, load average: 3.45, 2.89, 1.51
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND
6560 root 31 0 2892 1236 1032 R 82 0.1 1:50.24 1 sh
6558 root 28 0 1428 276 228 S 42 0.0 1:00.09 1 f
6557 root 30 0 1424 280 228 R 35 0.0 1:00.25 0 f
6559 root 39 0 1424 276 228 R 33 0.0 0:58.36 0 f
6560 sh is asking for 100% cpu on cpu number 1
6558 f is asking for 50% cpu on cpu number 1
6557 f is asking for 50% cpu on cpu number 0
6559 f is asking for 50% cpu on cpu number 0
So if 6560 and 6558 are asking for cpu from cpu number 1:
6560 wants 100% and 6558 wants 50%.
6560 should get 2/3 cpu 6558 should get 1/3 cpu
2.6.21-rc3-rsdl-smp gives 65% sh and 35% f
patched 2.6.21-rc3-rsdl-smp gives 60% sh and 40% f
2.6.20.3-smp gives 51% sh and 49% f
We think cpu correctness is 2.6.21-rc3-rsdl-smp
in that test.
Xant
____________________________________________________________________________________
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367
next reply other threads:[~2007-03-30 15:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 15:05 Xenofon Antidides [this message]
2007-03-30 16:46 ` [test] hackbench.c interactivity results: vanilla versus SD/RSDL Mike Galbraith
2007-03-31 2:36 ` Xenofon Antidides
2007-03-31 3:23 ` Mike Galbraith
2007-03-31 3:42 ` Mike Galbraith
2007-03-31 6:08 ` Mike Galbraith
2007-03-31 5:41 ` Xenofon Antidides
2007-03-31 6:31 ` Mike Galbraith
2007-03-31 6:49 ` Mike Galbraith
2007-03-31 9:28 ` Xenofon Antidides
2007-03-31 9:43 ` Ingo Molnar
2007-03-31 9:48 ` [patch] sched: improve fairness, v3 Ingo Molnar
2007-03-31 10:11 ` Ingo Molnar
2007-03-31 10:05 ` [test] hackbench.c interactivity results: vanilla versus SD/RSDL Ingo Molnar
2007-04-03 2:34 ` Con Kolivas
2007-04-03 5:24 ` Mike Galbraith
2007-03-31 5:04 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2007-03-29 11:22 Ingo Molnar
2007-04-03 1:07 ` 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=325618.89505.qm@web26701.mail.ukl.yahoo.com \
--to=xantidides@yahoo.gr \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).