All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Clark Williams <williams@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] 4.4-rc6-rt1
Date: Wed, 13 Jan 2016 18:58:45 +0100	[thread overview]
Message-ID: <20160113175845.GK29964@linutronix.de> (raw)
In-Reply-To: <1451632781.9800.22.camel@gmail.com>

* Mike Galbraith | 2016-01-01 08:19:41 [+0100]:

>>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                      
>>     3 root      -2   0       0      0      0 S  37.3  0.0 307:52.44 ksoftirqd/0                  
>>    32 root      -2   0       0      0      0 S  37.3  0.0 308:08.72 ksoftirqd/2                  
>>    42 root      -2   0       0      0      0 R  37.3  0.0 308:32.84 ksoftirqd/3                  
>>    22 root      -2   0       0      0      0 S  26.9  0.0 222:29.82 ksoftirqd/1                  
>>     1 root      20   0   46628   6980   4976 S   1.3  0.2   0:13.98 systemd                      
>> 22358 williams  20   0  159980   4552   3780 R   1.0  0.1   0:00.39 top       
>
>Heh, I didn't notice immediately because I throttle nohz, am seeing
>only tiny utilization (but nohz idle isn't working).  With throttle
>patch removed, box is screaming, expires=4294990471 pokes eyeball.

This is due to NO_HZ as far as I can tell. My AMD A10 in idle mode has
0.7% utilisation of ksoftirqd/ with CONFIG_HZ_PERIODIC and with
CONFIG_NO_HZ_FULL it shows about 25% on all CPU threads.

Sebastian

  parent reply	other threads:[~2016-01-13 17:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 22:57 [ANNOUNCE] 4.4-rc6-rt1 Sebastian Andrzej Siewior
2015-12-31 16:24 ` Clark Williams
2016-01-01  7:19   ` Mike Galbraith
2016-01-01  9:14     ` Thomas Gleixner
2016-01-01  9:45       ` Mike Galbraith
     [not found]     ` <568CF08F.3070001@caviumnetworks.com>
2016-01-13 11:45       ` [ANNOUNCE] 4.4-rc6-rt1 (arm64) Jaggi, Manish
2016-01-13 13:45         ` Sebastian Andrzej Siewior
2016-01-14 11:50           ` Jaggi, Manish
2016-01-13 17:58     ` Sebastian Andrzej Siewior [this message]
2016-01-13 18:36       ` [ANNOUNCE] 4.4-rc6-rt1 Grygorii Strashko
2016-01-14 14:59         ` Sebastian Andrzej Siewior
2016-01-14  9:33       ` Mike Galbraith
2016-01-14 14:17       ` Sebastian Andrzej Siewior
2016-01-14 14:29         ` Mike Galbraith
2016-01-14 14:30           ` Thomas Gleixner
2016-01-14 14:57             ` Mike Galbraith
2016-01-14 15:07               ` Thomas Gleixner
2016-01-14 16:05                 ` Mike Galbraith
2016-01-16 13:23                   ` Mike Galbraith
2016-01-16 13:43                     ` Thomas Gleixner
2016-01-16 13:52                       ` Mike Galbraith
2016-01-16 13:59                         ` Thomas Gleixner
2016-01-16 14:09                           ` Mike Galbraith
2016-01-07 12:15 ` Tim Sander
2016-01-13 13:40   ` Sebastian Andrzej Siewior
2016-01-22 15:35 ` Grygorii Strashko
2016-01-22 15:48   ` Sebastian Andrzej Siewior
2016-01-22 20:44     ` Sebastian Andrzej Siewior

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=20160113175845.GK29964@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=umgwanakikbuti@gmail.com \
    --cc=williams@redhat.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 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.