LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Ingo Molnar <mingo@elte.hu>
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: Tue, 3 Apr 2007 11:07:22 +1000 [thread overview]
Message-ID: <200704031107.22642.kernel@kolivas.org> (raw)
In-Reply-To: <20070329112249.GA32665@elte.hu>
On Thursday 29 March 2007 21:22, Ingo Molnar wrote:
> [ A quick guess: could SD's substandard interactivity in this test be
> due to the SMP migration logic inconsistencies Mike noticed? This is
> an SMP system and the hackbench workload is very scheduling intense
> and tasks are frequently queued from one CPU to another. ]
I assume you put it on and endless loop since hackbench 10 runs for .5 second
on my machine. Doubtful it's an SMP issue. update_if_moved should maintain
cross cpu scheduling decisions. The same slowdown would happen on UP and is
almost certainly due to the fact that hackbench 10 induces a load of _160_ on
the machine.
--
-ck
next prev parent reply other threads:[~2007-04-03 1:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 11:22 [test] hackbench.c interactivity results: vanilla versus SD/RSDL Ingo Molnar
2007-04-03 1:07 ` Con Kolivas [this message]
2007-03-30 15:05 Xenofon Antidides
2007-03-30 16:46 ` 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 10:05 ` Ingo Molnar
2007-04-03 2:34 ` Con Kolivas
2007-04-03 5:24 ` Mike Galbraith
2007-03-31 5:04 ` Nick Piggin
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=200704031107.22642.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--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).