From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Pavel Machek <pavel@ucw.cz>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mike Galbraith <mgalbraith@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: [PATCH] CPU hotplug: Slow down hotplug operations
Date: Sun, 11 May 2014 20:48:08 +0200 [thread overview]
Message-ID: <20140511184808.GC15527@pd.tnic> (raw)
In-Reply-To: <alpine.DEB.2.02.1405112026580.6261@ionos.tec.linutronix.de>
On Sun, May 11, 2014 at 08:29:30PM +0200, Thomas Gleixner wrote:
> On Sun, 11 May 2014, Pavel Machek wrote:
> > Well. If you add the delay, you'll mask real problems and cause regressions when
> > the delay is removed -- because fix-hotplug will probably take time to get right.
> >
> > Bad idea, AFAICT.
>
> Agreed, but Boris is right, that the current duct tape hackery needs
> to stop. And the delay was the desperate attempt to wake up people to
> focus on replacing the current mess instead of making it more
> entangled.
I think Pavel is missing the point: the delay will be removed with the
rewrite of cpu hotplug, after it actually works reliably. Then we won't
need delay anyway.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-05-11 18:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 19:57 [PATCH] CPU hotplug: Slow down hotplug operations Borislav Petkov
2014-05-07 20:06 ` Andrew Morton
2014-05-07 20:22 ` Thomas Gleixner
2014-05-07 20:26 ` Borislav Petkov
2014-05-11 17:02 ` Pavel Machek
2014-05-11 18:29 ` Thomas Gleixner
2014-05-11 18:48 ` Borislav Petkov [this message]
2014-05-12 20:56 ` Pavel Machek
2014-05-08 4:31 ` Srivatsa S. Bhat
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=20140511184808.GC15527@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=mgorman@suse.com \
--cc=mingo@kernel.org \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.