From: Joel Schopp <jschopp@austin.ibm.com>
To: Gautham R Shenoy <ego@in.ibm.com>
Cc: Nathan Lynch <ntl@pobox.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pseries: cpu: Reduce the polling interval in __cpu_up()
Date: Wed, 24 Jun 2009 11:39:09 -0500 [thread overview]
Message-ID: <4A4256AD.3080507@austin.ibm.com> (raw)
In-Reply-To: <20090624092637.32078.88042.stgit@sofia.in.ibm.com>
>
> The code needs testing on other powerpc platforms.
>
I think given the numbers you showed this is a good improvement, and it
clearly can't do any harm on platforms that implement msleep correctly.
For what it's worth:
Acked-by: Joel Schopp <jschopp@austin.ibm.com>
> Signed-off-by: Gautham R Shenoy <ego@in.ibm.com>
> ---
> arch/powerpc/kernel/smp.c | 5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/kernel/smp.c b/arch/powerpc/kernel/smp.c
> index 65484b2..00c13a1 100644
> --- a/arch/powerpc/kernel/smp.c
> +++ b/arch/powerpc/kernel/smp.c
> @@ -411,9 +411,8 @@ int __cpuinit __cpu_up(unsigned int cpu)
> * CPUs can take much longer to come up in the
> * hotplug case. Wait five seconds.
> */
> - for (c = 25; c && !cpu_callin_map[cpu]; c--) {
> - msleep(200);
> - }
> + for (c = 5000; c && !cpu_callin_map[cpu]; c--)
> + msleep(1);
> #endif
>
> if (!cpu_callin_map[cpu]) {
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
prev parent reply other threads:[~2009-06-24 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 9:26 [PATCH] pseries: cpu: Reduce the polling interval in __cpu_up() Gautham R Shenoy
2009-06-24 16:39 ` Joel Schopp [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=4A4256AD.3080507@austin.ibm.com \
--to=jschopp@austin.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ntl@pobox.com \
/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).