From: Mike Galbraith <mgalbraith@suse.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: RT <linux-rt-users@vger.kernel.org>, rostedt <rostedt@goodmis.org>
Subject: Re: jitter test scalability problem - my theory
Date: Fri, 29 Jul 2011 16:47:19 +0200 [thread overview]
Message-ID: <1311950839.30862.54.camel@marge.simson.net> (raw)
In-Reply-To: <1311950140.5890.365.camel@twins>
On Fri, 2011-07-29 at 16:35 +0200, Peter Zijlstra wrote:
> On Fri, 2011-07-29 at 16:31 +0200, Mike Galbraith wrote:
> > So it seems push/pull logic _may_ be my scalability problem. Even
> > though there's nothing that can be pushed/pulled, it's hammering a few
> > locks from many cores, so cores perturb each other enough despite
> > isolation, to fail once enough cores are active.
> >
> > Does that look like a reasonable explanation for my jitter increase?
>
> It is, Steve actually had patches for that..
Thanks for confirming.
I know a guy (me) who would _love_ to test them :) Diagnosing is one
thing, figuring out how to fix such an issue is quite another matter.
-Mike
prev parent reply other threads:[~2011-07-29 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 14:31 jitter test scalability problem - my theory Mike Galbraith
2011-07-29 14:35 ` Peter Zijlstra
2011-07-29 14:47 ` Mike Galbraith [this message]
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=1311950839.30862.54.camel@marge.simson.net \
--to=mgalbraith@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.