From: Alexey Vlasov <renton@renton.name>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Mike Galbraith <bitbucket@online.de>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel migration eat CPUs
Date: Wed, 4 Sep 2013 22:53:15 +0400 [thread overview]
Message-ID: <20130904185315.GB13294@beaver> (raw)
In-Reply-To: <20130825142837.GD31370@twins.programming.kicks-ass.net>
On Sun, Aug 25, 2013 at 04:28:37PM +0200, Peter Zijlstra wrote:
> and a function (or function-graph)
> trace for when this happens?
Unfortunately I could not make trace.
First when migration threads start to eat CPUs and when I turn on trace:
# echo function > current_tracer
# echo 1 > tracing_on
then server is down at once. LA comes up to several thousands, it stops
to receive commands. Sometimes I even have to reboot it.
And second when I manage to get trace then it shows little useful data.
https://www.dropbox.com/s/kxgwr9fuckddtgf/trace.txt.gz
Probably this junk appears from grsec patch? And I don't see migration
threads in it.
> Perhaps perf top -p <pick-a-thread> while the problem is happening will
> show something.
Also "perf top" doesn't show anything. It gives same values when
migration threads eat CPUs and when everything is OK on server.
=========================================
PerfTop: 68932 irqs/sec kernel:60.3% exact: 0.0% [4000Hz cycles], (all, 32 CPUs)
---------------------------------------------------------------------------------
64.11% [netconsole] [k] 0xffffffff81000de3
34.19% [unknown] [.] 0x0000000000585c45
0.40% libc-2.15.so [.] 0x0000000000124b10
0.23% perf [.] 0x000000000004df4f
0.14% ld-2.15.so [.] 0x00000000000183e7
0.08% libc-2.15.so [.] _nss_files_parse_grent
0.06% libc-2.15.so [.] _nss_files_parse_pwent
0.04% libc-2.15.so [.] memchr
0.04% php-cgi [.] match
0.03% libcrypt-2.15.so [.] 0x0000000000004eab
0.03% bash [.] 0x000000000001fe5a
0.02% libc-2.15.so [.] _IO_getline_info
0.02% php-cgi [.] php_pcre_exec
0.02% libc-2.15.so [.] _dl_addr
0.02% eaccelerator.so [.] eaccelerator_crc32
0.02% php-cgi [.] zend_hash_quick_find
0.02% libnss_compat-2.15.so [.] 0x00000000000055f1
0.01% php-cgi [.] zendparse
0.01% libc-2.15.so [.] fgets_unlocked
0.01% libnss_compat-2.15.so [.] _nss_compat_initgroups_dyn
=========================================
Now server is more loaded and eating CPUs by migration threads happens more often
and it lasts longer.
--
BRGDS. Alexey Vlasov.
next prev parent reply other threads:[~2013-09-04 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130823151711.f4c1f596b4c7aa1eecccc9a6@linux-foundation.org>
[not found] ` <20130825142837.GD31370@twins.programming.kicks-ass.net>
2013-08-29 10:10 ` Kernel migration eat CPUs Alexey Vlasov
2013-09-04 18:53 ` Alexey Vlasov [this message]
2013-09-05 11:12 ` Ingo Molnar
2013-09-11 15:18 ` Alexey Vlasov
2013-10-10 7:13 ` Alexey Vlasov
2013-08-22 15:00 Alexey Vlasov
2013-08-29 7:31 ` Mike Galbraith
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=20130904185315.GB13294@beaver \
--to=renton@renton.name \
--cc=akpm@linux-foundation.org \
--cc=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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