From: Mike Galbraith <mgalbraith@suse.de>
To: Borislav Petkov <bp@alien8.de>
Cc: lkml <linux-kernel@vger.kernel.org>, x86-ml <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Slow down stupid pounders
Date: Tue, 06 May 2014 14:42:33 +0200 [thread overview]
Message-ID: <1399380153.5192.219.camel@marge.simpson.net> (raw)
In-Reply-To: <20140506102924.GA25013@pd.tnic>
On Tue, 2014-05-06 at 12:29 +0200, Borislav Petkov wrote:
> Hi,
>
> so I'm getting sick'n'tired of all those bug reports of people pounding
> cpu hotplug with stupid scripts.
>
> * We know cpu hotplug is fragile/buggy/crap/needs proper rewrite.
>
> * Stupid hotplugging script doesn't resemble any real use case - go use
> a real benchmark/stress test to trigger bugs.
>
> So if we can't make pounders stop jerking off, let's make it
> uninterestingly slow. Stupid patch below, it might be completely idiotic
> to do it this way but at least starts the discussion about this being a
> really annoying issue which needs some sort of dealing with.
>
> I dunno, we can make it configurable (which will probably defeat its
> purpose partially), we can do some more fancy ratelimiting, per cpu,
> whatever... we'll see.
>
> Opinions, flames?
Damn. I was gonna suggest we shorten hours in -rt kernels to achieve my
full day stress testing survival goal.
-Mike
next prev parent reply other threads:[~2014-05-06 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:29 Slow down stupid pounders Borislav Petkov
2014-05-06 11:08 ` Steven Rostedt
2014-05-06 11:22 ` Borislav Petkov
2014-05-06 12:42 ` Mike Galbraith [this message]
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=1399380153.5192.219.camel@marge.simpson.net \
--to=mgalbraith@suse.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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 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.