From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Chris Metcalf <cmetcalf@mellanox.com>,
open list <linux-kernel@vger.kernel.org>,
Aaron Tomlin <atomlin@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kees Cook <keescook@chromium.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] ARM: smp: Remove CPU: shutdown notice
Date: Thu, 19 Jan 2017 21:07:44 +0900 [thread overview]
Message-ID: <20170119120744.GB435@tigerII.localdomain> (raw)
In-Reply-To: <1041c46f-13e7-4446-33e0-75eee9ffb91f@gmail.com>
On (01/18/17 11:56), Florian Fainelli wrote:
[..]
> >>> CPU hotplug isn't a fast operation anyway - it's also fairly disruptive
> >>> in that it uses stop_machine() to halt activity everywhere while taking
> >>> the CPU offline.
> >>
> >> We have a test that consists in shutting down all CPUs as frequently as
> >> we can and do this for about 2 million iterations which takes roughly
> >> 24h, and this printk slows thing down by a reasonable amount. Here are
> >> some numbers on 500 hotplug operations:
> >>
> >> w/ printk:
> >> real 0m9.997s
> >> user 0m0.725s
> >> sys 0m3.030s
> >> #
> >>
> >> w/o printk:
> >> real 0m8.547s
> >> user 0m0.436s
> >> sys 0m1.838s
> >
> > I am curious that a single printk() might make such a big difference.
>
> It does, because of how printk() is implemented (there is nothing wrong
> with it, just slow by nature and how the UART gets written to as well).
>
> >
> > One reason might be that the messages are pushed to a "slow" console.
>
> 115200 UART, yes that's slow, but not unusual.
>
> >
> > Another reason might be that there are many other messages printed
> > on the system and there is a contention on logbuf_lock or other
> > console related locks.
>
> The other messages being printed are those from the hotplug script that
> I run which just checkpoints its running every 50 instances, so it does
> not occur that often, the console really is not busy, which really
> extracts the overhead of printing "CPU: shutdown".
there is also console_cpu_notify(), which basically serializes all
CPU hotplug events. and that's a sleepable console_lock(), followed
by a potentially long console_unlock(). for hotplug each notification.
static int console_cpu_notify(unsigned int cpu)
{
if (!cpuhp_tasks_frozen) {
console_lock();
console_unlock();
}
return 0;
}
out of curiosity, does the change below improve anything in your test?
---
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index 7180088cbb23..72e86e06c4e4 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2035,8 +2035,9 @@ void resume_console(void)
static int console_cpu_notify(unsigned int cpu)
{
if (!cpuhp_tasks_frozen) {
- console_lock();
- console_unlock();
+ /* If trylock fails, someone else is doing the printing */
+ if (console_trylock())
+ console_unlock();
}
return 0;
}
next prev parent reply other threads:[~2017-01-19 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 23:07 [PATCH] ARM: smp: Remove CPU: shutdown notice Florian Fainelli
2017-01-17 23:23 ` Russell King - ARM Linux
2017-01-17 23:39 ` Florian Fainelli
2017-01-18 9:55 ` Petr Mladek
2017-01-18 19:56 ` Florian Fainelli
2017-01-19 12:07 ` Sergey Senozhatsky [this message]
2017-01-18 22:39 ` Russell King - ARM Linux
2017-01-18 22:49 ` Florian Fainelli
2017-01-18 22:53 ` [PATCH] ARM: Reduce "CPU: shutdown" message to debug level Florian Fainelli
2017-01-18 23:20 ` Russell King - ARM Linux
2017-01-19 0:27 ` Florian Fainelli
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=20170119120744.GB435@tigerII.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=cmetcalf@mellanox.com \
--cc=f.fainelli@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pmladek@suse.com \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=tglx@linutronix.de \
/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