From: Borislav Petkov <bp@alien8.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: lkml <linux-kernel@vger.kernel.org>, x86-ml <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.com>,
Mike Galbraith <mgalbraith@suse.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Slow down stupid pounders
Date: Tue, 6 May 2014 13:22:04 +0200 [thread overview]
Message-ID: <20140506112204.GB25013@pd.tnic> (raw)
In-Reply-To: <20140506070854.757fd3ea@gandalf.local.home>
On Tue, May 06, 2014 at 07:08:54AM -0400, Steven Rostedt wrote:
> Hey, I'm one of those that jerk off to CPU hotplug stress test scripts!
I know you are, Mike gave me your script. Like you haven't done enough!
:-P
> We were just bitching about this yesterday, but -rt related. As
> anything crap in mainline just becomes exponentially more crap in -rt.
> The CPU hotplug case becomes a mountain of crap that we just dig
> tunnels through to get by.
>
> A while ago Thomas had a proof of concept patch I believe that was
> suppose to pick up traction but unfortunately never went anywhere, even
> after being told it would.
>
> The real option is to rewrite cpu hotplug.
I know, and we might get lucky, after all.
I'm proposing this as a temporary thing until we have the real deal in
place. I simply would like to shoo those pounding beaks in the interim.
:-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-05-06 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:29 Borislav Petkov
2014-05-06 11:08 ` Steven Rostedt
2014-05-06 11:22 ` Borislav Petkov [this message]
2014-05-06 12:42 ` Mike Galbraith
2014-05-06 15:08 ` Mike Galbraith
2014-05-06 16:10 ` Borislav Petkov
2014-06-14 20:32 ` Pavel Machek
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=20140506112204.GB25013@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=mgorman@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®